From: Ophir Munk <ophirmu@mellanox.com>
To: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
Ophir Munk <ophirmu@mellanox.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Viktorin <viktorin@rehivetech.com>,
Jianbo Liu <jianbo.liu@arm.com>
Subject: [dpdk-dev] [PATCH v1] net/tap: add eBPF ARM and POWERPC architectures support
Date: Wed, 31 Jan 2018 13:44:46 +0000 [thread overview]
Message-ID: <1517406286-4306-1-git-send-email-ophirmu@mellanox.com> (raw)
This commit adds eBPF system call definitions for ARM and POWERPC
architectures.
Old Linux header files may not define eBPF system call numbers.
In order to enable a successful eBPF compilation on all Linux
platforms - the missing system call definitions are explicitly added.
#elif defined(__powerpc__)
# define __NR_bpf 361
#elif defined(__arm__)
# define __NR_bpf 386
Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
---
drivers/net/tap/tap_bpf.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/tap/tap_bpf.h b/drivers/net/tap/tap_bpf.h
index 8d6f9a2..58e6d25 100644
--- a/drivers/net/tap/tap_bpf.h
+++ b/drivers/net/tap/tap_bpf.h
@@ -97,6 +97,10 @@ union bpf_attr {
# define __NR_bpf 349
# elif defined(__s390__)
# define __NR_bpf 351
+# elif defined(__powerpc__)
+# define __NR_bpf 361
+# elif defined(__arm__)
+# define __NR_bpf 386
# else
# error __NR_bpf not defined
# endif
--
2.7.4
next reply other threads:[~2018-01-31 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 13:44 Ophir Munk [this message]
2018-01-31 14:28 ` 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=1517406286-4306-1-git-send-email-ophirmu@mellanox.com \
--to=ophirmu@mellanox.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@arm.com \
--cc=olgas@mellanox.com \
--cc=pascal.mazon@6wind.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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).