From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E5487A0093 for ; Fri, 11 Mar 2022 02:19:00 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6815C40E78; Fri, 11 Mar 2022 02:19:00 +0100 (CET) Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com [209.85.214.173]) by mails.dpdk.org (Postfix) with ESMTP id E416B40042 for ; Fri, 11 Mar 2022 02:18:58 +0100 (CET) Received: by mail-pl1-f173.google.com with SMTP id p17so6411037plo.9 for ; Thu, 10 Mar 2022 17:18:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Lwp5NP/YWlZFyGe+AXcw0zXunVbUn7tlkPJdN55+aSQ=; b=Ucc/2JEvWHG4bYEsCwBk/jV+7UcSPf/ItrGw5eoTKpXA4sKKDiZ88HYK10+Bitg/Zm n6k49OypAIP8dDRR+UdA3Yqpe/fZ/yMJby5ZrgH1vOAMJbub3HJWbhYcNFoB97rOoV9Z v/7yZWrqNrUUb6TBmiMoZwiG/TfSoiSLKy5JWiEjNO5F2KoWwfYvUXdGxuu+mHUzwnOe RkR5A86oztcSZ+Xu7U59fJ3L3iXowMkRMou4QaNAjc9yt4B7VSG2pXUQHDJK8oROGyog atSQpdP9aSlaJe7pMO9QqfuhnTPO+42XANlwhBFdVi692TFu6KFHzAMGH4aSvIc0pDcp vO9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Lwp5NP/YWlZFyGe+AXcw0zXunVbUn7tlkPJdN55+aSQ=; b=s/5N1dicuypwwIPHHi/L07K1mdNGLrUJZGdg2Tsd8/LNPvp68TtUdEJR0RqbfmDy1+ u4dQ4Gp0vjFUT/AbeiC7PWau1ORqFRgkBGjJTmh5DQtWOzzpgV00jGPRw0Z8HY2z+8Hm DRx2H/32r5I2hYxzlOo4BKr/exEuT9mF4R4WfhtFDMGbzoKHhK9E9dWoRqxvjrfP8wrh XHwfok0DhAeUvjpB6CxsBkOkuW1vNKuGtJPdjftTNya67BqSUaz6XsqUWfq3wc2XobO/ Cjkd5y3PdWfP2HNiZA+E2uFZUzYYf7dw1s6E58oF6u7HxGhxUanthlKsXbOWXWRiaKyf ksiw== X-Gm-Message-State: AOAM531KDa+j3fDUISEPF+C/AgKU6wiuPFTpirkx0PnDHxFu5zepZQSi i0Zg40R9LuJJDq17JTHxV9O7W695qhKHCw== X-Google-Smtp-Source: ABdhPJxEZFqcGrIIyyY9zy8hL6CJc1OP/T2vvjS9X92NPbBh0uRWO+3stIQKjqthl3l4UGLsE5iuVA== X-Received: by 2002:a17:902:9043:b0:14f:aa08:8497 with SMTP id w3-20020a170902904300b0014faa088497mr7699017plz.109.1646961538031; Thu, 10 Mar 2022 17:18:58 -0800 (PST) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id mw7-20020a17090b4d0700b001b8baf6b6f5sm7533622pjb.50.2022.03.10.17.18.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Mar 2022 17:18:57 -0800 (PST) Date: Thu, 10 Mar 2022 17:18:54 -0800 From: Stephen Hemminger To: Dan Gora Cc: "Sanford, Robert" , "users@dpdk.org" Subject: Re: meson options - build vs target machine cpuflags question Message-ID: <20220310171854.272f459b@hermes.local> In-Reply-To: References: <165CAE28-2A3E-4960-8E57-2EB9A19024DB@akamai.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Thu, 10 Mar 2022 19:54:48 -0300 Dan Gora wrote: > On Thu, Mar 10, 2022 at 11:46 AM Sanford, Robert wrote: > > > > Hello All, > > > > We build a DPDK 21.05 app on Intel x86 machines with RDSEED in cpuflags, and may run it on machines *without* RDSEED. > > This results in a fatal error ... > > ERROR: This system does not support "RDSEED". > > Please check that RTE_MACHINE is set correctly. > > EAL: FATAL: unsupported cpu type. > > > > I try adding -Dplatform=haswell when running meson, (because gcc man page indicates that haswell is last arch w/o RDSEED) but get the same result. > > Until we resolve it, our workaround is changing the error-out in rte_cpu_is_supported() to just print a warning and continue. > > We don't have direct access to automated build machines, we go through change request processes, and so we can't rapidly try too many things. > > > > Is there a better meson option, such as machine=haswell, or something else that will work? > > > > Thanks in advance, > > Robert Sanford > > I tried four times to get a simple fix for this (and the lack of > getentropy() on older glibc) to determine the entropy source at run > time and got nothing but an endless raft of shit and ridiculous > criticisms that I completely gave up trying to contribute to DPDK ever > again. > > The DPDK developers think that it's your responsibility to have a > separate build system for each of your target systems and platforms > and that if you don't you're basically a big dummy. > > Don't believe me? Go look through the archives: > > "[PATCH 2/2] eal: resolve getentropy at run time for random seed" > "[PATCH v4 2/2] eal: emulate glibc getentropy for initial random seed". > > I suggest that you just fork DPDK and use one of those patches and > just maintain a separate DPDK tree. That's what I did. It's way > easier than trying to get anything upstream. > > thanks > dan The ideal solution would be able to use gcc function attributes and dyanmic linking to do this at runtime - ie multiversion library. But this opens a set of different problems like compiler versions and testing.