From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by dpdk.org (Postfix) with ESMTP id 00DA19A for ; Wed, 8 Jan 2014 07:12:24 +0100 (CET) Received: by mail-lb0-f169.google.com with SMTP id u14so979151lbd.14 for ; Tue, 07 Jan 2014 22:13:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XpR++goDyr97PjRYcKwAo6mup6+Llg8zrSBPHRXOiaQ=; b=a+DhXQ6KzzbGZxyKjIYv9b4DF8eI5EO2uQweyYp8bpk5t4VDUMZJxR3vGc2aKLAUn7 mM+JrkA9QFZd2lpTqp+lOTrDGHAvzgnRltU5d5abfWWg3GzfbQsZmF7/eDRaqykzSu4k o6eoIfR5yygO187v5CBsHgib+gFvGtyRdw2aAsNhi0wjcjiI9uD2Pt8ZyjpQa0KDORw3 SoNVRCJw1ioQMw1vVxs39zPTOPZmtEosgyZVpTkqitfLDRzjLCXAMUeEWS/du3AXUUIP 5e8CfKrjNchX70vnL0kuTJjPbtBB9Vbh0azWS97vH0/GRpO8jCDxPoATVD+KeKqxUQYe gkjw== MIME-Version: 1.0 X-Received: by 10.152.203.129 with SMTP id kq1mr4362123lac.77.1389161616354; Tue, 07 Jan 2014 22:13:36 -0800 (PST) Received: by 10.114.59.164 with HTTP; Tue, 7 Jan 2014 22:13:36 -0800 (PST) In-Reply-To: References: <1734676.i5HPyu6JDa@x220> Date: Wed, 8 Jan 2014 14:13:36 +0800 Message-ID: From: Jose Gavine Cueto To: Thomas Monjalon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] intel x540-at2 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 06:12:25 -0000 Hi, Just to let you know that the invalid instruction error above went away when AVX was enabled using host model cpu mode in the VM. Thanks, Pepe On Mon, Jan 6, 2014 at 2:03 PM, Jose Gavine Cueto wrote: > Hi Thomas, > > On Sun, Jan 5, 2014 at 10:54 PM, Thomas Monjalon < > thomas.monjalon@6wind.com> wrote: > >> 05/01/2014 22:31, Jose Gavine Cueto : >> > venky.venkatesan@intel.com> wrote: >> > > Was the DPDK library compiled on a different machine and the used in >> the >> > > VM? It looks like it has been compiled for native AVX (hence the >> > > vzeroupper). Could you dump cpuinfo in the VM and see what >> instruction set >> > > the VM supports? >> > >> > Yes, it was compiled in a different machine and it was used in my VM. >> [...] >> > model name : Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz >> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge >> mca >> > cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm >> constant_tsc >> > rep_good nopl pni monitor ssse3 lahf_lm >> [...] >> > It seems that there is no avx here, does this mean this doesn't support >> > avx instructions ? >> >> Yes, you have no avx on this machine. >> Tip to clearly check this type of flag: >> grep --color -m1 avx /proc/cpuinfo >> >> So, you have 2 solutions: >> 1) build DPDK on this machine >> 2) build DPDK for a default machine: >> CONFIG_RTE_MACHINE=default >> defconfig files are wrongly called "default" but have CONFIG_RTE_MACHINE >> set to >> native. So the compilation flags are guessed from /proc/cpuinfo. You can >> look >> for AUTO_CPUFLAGS to better understand it. >> >> -- >> Thomas >> > > Thanks and I will try your suggestion. I will also post the result > whenever it is available, for the meantime I will be rebuilding the DPDK > lib. > > Cheers, > Pepe > > -- > To stop learning is like to stop loving. > -- To stop learning is like to stop loving.