DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: zhuangyan <zhuangyan@bytedance.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] vmovdqa64 instruction: how to be disabled in skylake CPU
Date: Wed, 2 Jan 2019 15:05:34 +0000	[thread overview]
Message-ID: <d8abe47d-3a00-0be1-3888-9dbe7244337c@intel.com> (raw)
In-Reply-To: <84917CEF-AC2A-4938-97A1-E9303A4CBA2D@bytedance.com>

On 12/23/2018 12:43 PM, zhuangyan wrote:
> Hello,
> 
> Is there any way to disable the generation of “vmovdqa64” instruction during the compilation of dpdk library on Intel Skylake CPU?
> 
> My dev VM uses Intel Skylake CPU while my test machine uses Intel uses Intel(R) Xeon(R) CPU E5-2630 v4 that is some sort of Intel Broadwell CPU.
> 
> And my generated executable file of dpdk application contains "vmovdqa64" instruction that is NOT supported in Intel Broadwell CPU so my dpdk application fails to be run.
> 
> I tried MACHINE_CFLAGS= -march=native/broadwell/ivybridge within dpdk-stable-17.11.2/mk/machine/native/rte.vars.mk, however it does not work.
> 
> Additionally, my gcc version is gcc (Debian 4.9.2-10+deb8u1) 4.9.2.

In config file, it is possible to select machine type, via "CONFIG_RTE_MACHINE="
config option.

If it is "native", it will use all available CPU features host machine supports.
For portability there is also "default" machine type, which will build for
"corei7", this should work for your case.

You can check available machine types at: 'mk/machine/*'

      reply	other threads:[~2019-01-02 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23 12:43 zhuangyan
2019-01-02 15:05 ` Ferruh Yigit [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=d8abe47d-3a00-0be1-3888-9dbe7244337c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=zhuangyan@bytedance.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).