From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by dpdk.org (Postfix) with ESMTP id 958C2DE4 for ; Sun, 5 Jan 2014 15:30:13 +0100 (CET) Received: by mail-lb0-f171.google.com with SMTP id w7so9145092lbi.2 for ; Sun, 05 Jan 2014 06:31:24 -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=F7Wan1x60X5iOLxUvo/LJ+rRN0ojZh80vGk1dw7cbAk=; b=LtuShrO2t1p9ukyq4ME1hx6EktvQET8JffWzTmlcwP9utFVaChvYb2LpMXLfQWmqZC hzRQ55CDfsK6ACKdBhqJ5bIa42PNrh1Wbkna8TOQE6b7jfaBwhrKAt9rgDtuM5WgKGDQ PhEXJe/HbNRhE4p+oIf1wZAk2VhKiDzrRtFDfC66e1u9XqAYOgdJAI7ay9NjBENfUS2G YSv8YNpRze8FdBdcFrw5RkhUESdLdKnbMcEQY7fxM+5K4beqTd3lv5ollWOF+KouR7nc cFbJsdRrYB5lfnbh27y03/I585qi86/FeV7KEaME7XLTVR+JCXo0ngFTyxhakJqGKOz6 LXig== MIME-Version: 1.0 X-Received: by 10.112.169.66 with SMTP id ac2mr5838850lbc.28.1388932284331; Sun, 05 Jan 2014 06:31:24 -0800 (PST) Received: by 10.114.59.164 with HTTP; Sun, 5 Jan 2014 06:31:24 -0800 (PST) In-Reply-To: References: <201401031056.16164.thomas.monjalon@6wind.com> <201401031126.10063.thomas.monjalon@6wind.com> Date: Sun, 5 Jan 2014 22:31:24 +0800 Message-ID: From: Jose Gavine Cueto To: "Venkatesan, Venky" 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: Sun, 05 Jan 2014 14:30:14 -0000 Hi Venky, On Fri, Jan 3, 2014 at 9:43 PM, Venkatesan, Venky < venky.venkatesan@intel.com> wrote: > Pepe , > > 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. I don't have cpuinfo prog as of the moment so I've pasted my VM's cpuinfo file instead. processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz stepping : 9 cpu MHz : 2658.957 cache size : 6144 KB fpu : yes fpu_exception : yes cpuid level : 5 wp : yes 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 bogomips : 5317.91 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: It seems that there is no avx here, does this mean this doesn't support avx instructions ? Thanks, Pepe > > -Venky > > Sent from my iPhone > > > On Jan 3, 2014, at 2:32 AM, "Jose Gavine Cueto" > wrote: > > > > I haven't added it yet, because as of the moment I do not have an access > to > > the built DPDK library I was using. I was just linking it with my DPDK > > application. > > > > I tried to debug it with GDB and disassembled it, the invalid instruction > > was "vzeroupper" which occurs at rte_eal_init, somewhere when > initializing > > pthreads. > > > > Ok, I'll to debug more and get more information. > > > > Thanks again, > > Pepe > > > > > > On Fri, Jan 3, 2014 at 6:26 PM, Thomas Monjalon > > wrote: > > > >> 03/01/2014 11:09, Jose Gavine Cueto : > >>> I am running a DPDK application in a guest VM which uses one VF. This > VM > >>> runs on top of the host that has an x540-at2 NIC and uses the ixgbe > >> driver. > >>> The issue was that every time I run the DPDK application in the VM it > >>> errors an invalid instruction and stops there. > >> > >> First, have you added x540-at2 in ixgbe_type.h, ixgbe_api.c and > >> rte_pci_dev_ids.h ? > >> What is the invalid instruction ? Have you tried to debug it ? > >> > >> I don't know this NIC so I'm afraid you should debug it by yourself. > >> > >> Please, keep us informed if you make it working. > >> -- > >> Thomas > > > > > > > > -- > > To stop learning is like to stop loving. > -- To stop learning is like to stop loving.