patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <>
Subject: [dpdk-stable] [PATCH v16 3/8] net/virtio: fix aarch32 build
Date: Tue, 20 Apr 2021 12:45:12 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

NEON vector path of the PMD needs aarch64 support. But it was
enabled for aarch32 build as well because aarch32 build had
cpu_family set to aarch64. So build for aarch32 will fail due
to unsupported intrinsics.

Fix aarch32 build by updating meson file to exclude NEON vector
implementation for aarch32.

Fixes: 749799482a72 ("net/virtio: add to meson build")

Signed-off-by: Juraj Linkeš <>
 drivers/net/virtio/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/virtio/ b/drivers/net/virtio/
index d595cfdcab..88e231565e 100644
--- a/drivers/net/virtio/
+++ b/drivers/net/virtio/
@@ -39,7 +39,7 @@ if arch_subdir == 'x86'
 	sources += files('virtio_rxtx_simple_sse.c')
 elif arch_subdir == 'ppc'
 	sources += files('virtio_rxtx_simple_altivec.c')
-elif arch_subdir == 'arm' and host_machine.cpu_family().startswith('aarch64')
+elif arch_subdir == 'arm' and dpdk_conf.get('RTE_ARCH_64')
 	sources += files('virtio_rxtx_packed.c')
 	sources += files('virtio_rxtx_simple_neon.c')

  parent reply	other threads:[~2021-04-20 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-04-20 10:45 ` [dpdk-stable] [PATCH v16 1/8] net/sfc: " Juraj Linkeš
2021-04-20 10:45 ` [dpdk-stable] [PATCH v16 2/8] net/bnxt: " Juraj Linkeš
2021-04-20 10:45 ` Juraj Linkeš [this message]
     [not found] <>
     [not found] ` <>
2021-04-21  8:50   ` [dpdk-stable] [PATCH v16 3/8] net/virtio: " Juraj Linkeš

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:

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

  git send-email \ \ \ \ \ \ \

* 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).