From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH 3/3] dma/idxd: fix non-AVX builds with older compilers
Date: Fri, 24 Jun 2022 08:24:02 +0000 [thread overview]
Message-ID: <BYAPR11MB2711E65C61D7F1D302623F45FEB49@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220623134933.469240-4-bruce.richardson@intel.com>
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Thursday, June 23, 2022 9:50 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>
> Subject: [PATCH 3/3] dma/idxd: fix non-AVX builds with older compilers
>
> When building without AVX2 support using an older compiler e.g. gcc 4.8 on
> Centos/RHEL 7, we get build errors due to the use of AVX2 intrinsics.
> This is because the compiler does not support
> "__attribute__((target(AVX2)))" function attribute. Disable build of this
> driver such edge cases.
>
> Generic builds using recent compilers, and all builds with a minimum baseline
> of AVX2 are unaffected by this change.
>
> Fixes: aa802b10237c ("dma/idxd: fix AVX2 in non-datapath functions")
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
Tested-by: Yu Jiang <YuX.Jiang@intel.com>
Tested env as below:
OS: CentOS7.9/kernel: 3.10.0-1160.62.1.el7.x86_64
Compiler: gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC)
Best regards,
Yu Jiang
next prev parent reply other threads:[~2022-06-24 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 13:49 [PATCH 0/3] fix misc dma driver build errors Bruce Richardson
2022-06-23 13:49 ` [PATCH 1/3] raw/ioat: fix build error for missing errno Bruce Richardson
2022-06-23 13:49 ` [PATCH 2/3] raw/ioat: fix build when ioat dmadev enabled Bruce Richardson
2022-06-23 13:49 ` [PATCH 3/3] dma/idxd: fix non-AVX builds with older compilers Bruce Richardson
2022-06-24 8:24 ` Jiang, YuX [this message]
2022-06-26 8:29 ` Thomas Monjalon
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=BYAPR11MB2711E65C61D7F1D302623F45FEB49@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).