From: Stanislaw Kardach <kda@semihalf.com>
To: Jakub Grajciar <jgrajcia@cisco.com>
Cc: Stanislaw Kardach <kda@semihalf.com>,
dev@dpdk.org, Frank Zhao <Frank.Zhao@starfivetech.com>,
Sam Grove <sam.grove@sifive.com>,
mw@semihalf.com, upstream@semihalf.com
Subject: [PATCH RESEND v4 3/8] net/memif: set memfd syscall ID on RISC-V
Date: Tue, 7 Jun 2022 12:46:12 +0200 [thread overview]
Message-ID: <20220607104617.153892-4-kda@semihalf.com> (raw)
In-Reply-To: <20220607104617.153892-1-kda@semihalf.com>
Define the missing __NR_memfd_create syscall id to enable the memif PMD.
Sponsored-by: Frank Zhao <Frank.Zhao@starfivetech.com>
Sponsored-by: Sam Grove <sam.grove@sifive.com>
Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
---
drivers/net/memif/meson.build | 5 -----
drivers/net/memif/rte_eth_memif.h | 2 ++
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/net/memif/meson.build b/drivers/net/memif/meson.build
index 9afb495953..680bc8631c 100644
--- a/drivers/net/memif/meson.build
+++ b/drivers/net/memif/meson.build
@@ -5,11 +5,6 @@ if not is_linux
build = false
reason = 'only supported on Linux'
endif
-if arch_subdir == 'riscv'
- build = false
- reason = 'riscv arch not supported'
- subdir_done()
-endif
sources = files(
'memif_socket.c',
diff --git a/drivers/net/memif/rte_eth_memif.h b/drivers/net/memif/rte_eth_memif.h
index a5ee23d42e..81e7dceae0 100644
--- a/drivers/net/memif/rte_eth_memif.h
+++ b/drivers/net/memif/rte_eth_memif.h
@@ -180,6 +180,8 @@ const char *memif_version(void);
#define __NR_memfd_create 360
#elif defined __i386__
#define __NR_memfd_create 356
+#elif defined __riscv
+#define __NR_memfd_create 279
#else
#error "__NR_memfd_create unknown for this architecture"
#endif
--
2.30.2
next prev parent reply other threads:[~2022-06-07 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 10:46 [PATCH RESEND v4 0/8] Introduce support for RISC-V architecture Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 1/8] eal: add initial " Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 2/8] net/ixgbe: enable vector stubs for RISC-V Stanislaw Kardach
2022-06-07 10:46 ` Stanislaw Kardach [this message]
2022-06-07 10:46 ` [PATCH RESEND v4 4/8] net/tap: set BPF syscall ID " Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 5/8] examples/l3fwd: enable RISC-V operation Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 6/8] test/cpuflags: add test for RISC-V cpu flag Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 7/8] devtools: add RISC-V to test-meson-builds.sh Stanislaw Kardach
2022-06-07 10:46 ` [PATCH RESEND v4 8/8] ci: add RISCV64 cross compilation job Stanislaw Kardach
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=20220607104617.153892-4-kda@semihalf.com \
--to=kda@semihalf.com \
--cc=Frank.Zhao@starfivetech.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=mw@semihalf.com \
--cc=sam.grove@sifive.com \
--cc=upstream@semihalf.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).