From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id F14A78E6E for ; Thu, 26 Apr 2018 18:34:42 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2018 09:34:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,330,1520924400"; d="scan'208";a="49369272" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.51]) by fmsmga004.fm.intel.com with SMTP; 26 Apr 2018 09:34:39 -0700 Received: by (sSMTP sendmail emulation); Thu, 26 Apr 2018 17:34:38 +0100 Date: Thu, 26 Apr 2018 17:34:38 +0100 From: Bruce Richardson To: Riccardo Ravaioli Cc: dev@dpdk.org Message-ID: <20180426163437.GA84332@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH] AVX check X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2018 16:34:43 -0000 On Thu, Apr 26, 2018 at 06:06:47PM +0200, Riccardo Ravaioli wrote: > Hi all, > > I need to install DPDK on 64-bit Linux machines whose processors might or > might not support AVX instructions. In my current configuration file, > defconfig_x86-64-native-linuxapp-gcc, the parameter CONFIG_RTE_MACHINE is > set to native. If I compile DPDK on a machine that supports AVX and then I > install it (along with openvswitch) on a machine that does *not* support > AVX, openvswitch won't start and will output an "illegal instruction" > error. > > I'm proposing the following patch to fix this issue: > Hi, rather than changing the code, the best way to handle this is to change the build target to something other than "native" in the build config file. I would suggest "nehalem" as a suitable MACHINE type value. This provides SSE4.x support, but no AVX. /Bruce