From: allanzhang <allanzhang@google.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: allanzhang <allanzhang@google.com>
Subject: [PATCH bpf-next v6 0/2] bpf: Allow bpf_skb_event_output for more prog types
Date: Tue, 25 Jun 2019 17:38:50 -0700 [thread overview]
Message-ID: <20190626003852.163986-1-allanzhang@google.com> (raw)
Software event output is only enabled by a few prog types right now (TC,
LWT out, XDP, sockops). Many other skb based prog types need
bpf_skb_event_output to produce software event.
More prog types are enabled to access bpf_skb_event_output in this
patch.
v2 changes:
Reformating log message.
v3 changes:
Reformating log message.
v4 changes:
Reformating log message.
v5 changes:
Fix typos, reformat comments in event_output.c, move revision history to
cover letter.
v6 changes:
fix Signed-off-by, fix fixup map creation.
allanzhang (2):
bpf: Allow bpf_skb_event_output for a few prog types
bpf: Add selftests for bpf_perf_event_output
net/core/filter.c | 6 ++
tools/testing/selftests/bpf/test_verifier.c | 12 ++-
.../selftests/bpf/verifier/event_output.c | 94 +++++++++++++++++++
3 files changed, 111 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/bpf/verifier/event_output.c
--
2.22.0.410.gd8fdbe21b5-goog
next reply other threads:[~2019-06-26 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 0:38 allanzhang [this message]
2019-06-26 0:38 ` [PATCH bpf-next v6 1/2] bpf: Allow bpf_skb_event_output for a few prog types allanzhang
2019-06-26 0:38 ` [PATCH bpf-next v5 2/2] bpf: Add selftests for bpf_perf_event_output allanzhang
2019-06-26 1:35 ` [PATCH bpf-next v6 0/2] bpf: Allow bpf_skb_event_output for more prog types Song Liu
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=20190626003852.163986-1-allanzhang@google.com \
--to=allanzhang@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).