DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/3] fix misc dma driver build errors
Date: Thu, 23 Jun 2022 14:49:30 +0100	[thread overview]
Message-ID: <20220623134933.469240-1-bruce.richardson@intel.com> (raw)

The use of function attributes to enable AVX2 on idxd builds is not
supported by older compilers, so we need additional checks in the
dma/idxd driver to disable that in cases where it is not buildable.

This fix revealed further issues with the older rawdev driver, which
only gets build when the dma driver is disabled.

Bruce Richardson (3):
  raw/ioat: fix build error for missing rte_errno
  raw/ioat: fix build when ioat dmadev enabled
  dma/idxd: fix non-AVX builds with older compilers

 drivers/dma/idxd/meson.build           | 11 +++++++++++
 drivers/raw/ioat/ioat_common.c         |  2 ++
 drivers/raw/ioat/ioat_private.h        |  4 ++--
 drivers/raw/ioat/ioat_rawdev.c         |  2 --
 drivers/raw/ioat/rte_idxd_rawdev_fns.h |  1 +
 5 files changed, 16 insertions(+), 4 deletions(-)

--
2.34.1


             reply	other threads:[~2022-06-23 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 13:49 Bruce Richardson [this message]
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
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=20220623134933.469240-1-bruce.richardson@intel.com \
    --to=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).