DPDK patches and discussions
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Build failure in v2.0.0-rc3 with !CC_AVX2_SUPPORT
Date: Tue, 31 Mar 2015 10:27:17 -0500	[thread overview]
Message-ID: <20150331152717.GC99112@ubuntu-hedt> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772582141330E@irsmsx105.ger.corp.intel.com>

On Tue, Mar 31, 2015 at 02:59:36PM +0000, Ananyev, Konstantin wrote:
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Seth Forshee
> > Sent: Tuesday, March 31, 2015 3:41 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] Build failure in v2.0.0-rc3 with !CC_AVX2_SUPPORT
> > 
> > I'm getting errors when building DPDK in an Ubuntu 15.04 VM with
> > T=x86_64-native-linuxapp-gcc. I've got a small VM set up without avx2 in
> > the cpu flags:
> > 
> >   $ cat /proc/cpuinfo
> >   processor       : 0
> >   vendor_id       : GenuineIntel
> >   cpu family      : 6
> >   model           : 6
> >   model name      : QEMU Virtual CPU version 2.0.0
> >   stepping        : 3
> >   microcode       : 0x1
> >   cpu MHz         : 2993.068
> >   cache size      : 4096 KB
> >   physical id     : 0
> >   siblings        : 1
> >   core id         : 0
> >   cpu cores       : 1
> >   apicid          : 0
> >   initial apicid  : 0
> >   fpu             : yes
> >   fpu_exception   : yes
> >   cpuid level     : 4
> >   wp              : yes
> >   flags           : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl
> > pni vmx cx16 x2apic popcnt hypervisor lahf_lm abm vnmi ept
> 
> 
> It seems that your VM cpu doesn't even have SSE3.
> As I remember, DPDK doesn't support architectures prior to SSE3, i.e you need a VM with at least core2 CPU.

This VM was set up with a script that just uses the qemu default CPU,
which is quite basic. Bumping it up to a core2 with SSE3 but not avx
does get the build working. So if that CPU lacks features required by
DPDK then I guess there's no problem, I just didn't know how to
interpret those build errors.

Thanks,
Seth

      reply	other threads:[~2015-03-31 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 14:41 Seth Forshee
2015-03-31 14:59 ` Ananyev, Konstantin
2015-03-31 15:27   ` Seth Forshee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150331152717.GC99112@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).