From: Song Liu <songliubraving@meta.com>
To: Yonghong Song <yhs@meta.com>
Cc: Jiri Olsa <olsajiri@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Martin Lau <kafai@meta.com>, Yonghong Song <yhs@meta.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Stanislav Fomichev <sdf@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH bpf-next 2/3] bpf: Add bpf_perf_event_read_sample() helper
Date: Thu, 3 Nov 2022 20:55:30 +0000 [thread overview]
Message-ID: <CF3D88C5-4D62-48E2-97AB-F6A7FF9CEF9D@fb.com> (raw)
In-Reply-To: <5b0152db-8a8e-0d8c-0304-8c48b735c3b7@meta.com>
> On Nov 3, 2022, at 12:45 PM, Yonghong Song <yhs@meta.com> wrote:
>
>
>
> On 11/1/22 3:02 AM, Jiri Olsa wrote:
>> On Mon, Oct 31, 2022 at 10:23:39PM -0700, Namhyung Kim wrote:
>>> The bpf_perf_event_read_sample() helper is to get the specified sample
>>> data (by using PERF_SAMPLE_* flag in the argument) from BPF to make a
>>> decision for filtering on samples. Currently PERF_SAMPLE_IP and
>>> PERF_SAMPLE_DATA flags are supported only.
>>>
>>> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>>> ---
>>> include/uapi/linux/bpf.h | 23 ++++++++++++++++
>>> kernel/trace/bpf_trace.c | 49 ++++++++++++++++++++++++++++++++++
>>> tools/include/uapi/linux/bpf.h | 23 ++++++++++++++++
>>> 3 files changed, 95 insertions(+)
>>>
>>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>>> index 94659f6b3395..cba501de9373 100644
>>> --- a/include/uapi/linux/bpf.h
>>> +++ b/include/uapi/linux/bpf.h
>>> @@ -5481,6 +5481,28 @@ union bpf_attr {
>>> * 0 on success.
>>> *
>>> * **-ENOENT** if the bpf_local_storage cannot be found.
>>> + *
>>> + * long bpf_perf_event_read_sample(struct bpf_perf_event_data *ctx, void *buf, u32 size, u64 sample_flags)
>>> + * Description
>>> + * For an eBPF program attached to a perf event, retrieve the
>>> + * sample data associated to *ctx* and store it in the buffer
>>> + * pointed by *buf* up to size *size* bytes.
>>> + *
>>> + * The *sample_flags* should contain a single value in the
>>> + * **enum perf_event_sample_format**.
>>> + * Return
>>> + * On success, number of bytes written to *buf*. On error, a
>>> + * negative value.
>>> + *
>>> + * The *buf* can be set to **NULL** to return the number of bytes
>>> + * required to store the requested sample data.
>>> + *
>>> + * **-EINVAL** if *sample_flags* is not a PERF_SAMPLE_* flag.
>>> + *
>>> + * **-ENOENT** if the associated perf event doesn't have the data.
>>> + *
>>> + * **-ENOSYS** if system doesn't support the sample data to be
>>> + * retrieved.
>>> */
>>> #define ___BPF_FUNC_MAPPER(FN, ctx...) \
>>> FN(unspec, 0, ##ctx) \
>>> @@ -5695,6 +5717,7 @@ union bpf_attr {
>>> FN(user_ringbuf_drain, 209, ##ctx) \
>>> FN(cgrp_storage_get, 210, ##ctx) \
>>> FN(cgrp_storage_delete, 211, ##ctx) \
>>> + FN(perf_event_read_sample, 212, ##ctx) \
>>> /* */
>>> /* backwards-compatibility macros for users of __BPF_FUNC_MAPPER that don't
>>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>>> index ce0228c72a93..befd937afa3c 100644
>>> --- a/kernel/trace/bpf_trace.c
>>> +++ b/kernel/trace/bpf_trace.c
>>> @@ -28,6 +28,7 @@
>>> #include <uapi/linux/bpf.h>
>>> #include <uapi/linux/btf.h>
>>> +#include <uapi/linux/perf_event.h>
>>> #include <asm/tlb.h>
>>> @@ -1743,6 +1744,52 @@ static const struct bpf_func_proto bpf_read_branch_records_proto = {
>>> .arg4_type = ARG_ANYTHING,
>>> };
>>> +BPF_CALL_4(bpf_perf_event_read_sample, struct bpf_perf_event_data_kern *, ctx,
>>> + void *, buf, u32, size, u64, flags)
>>> +{
>> I wonder we could add perf_btf (like we have tp_btf) program type that
>> could access ctx->data directly without helpers
>
> Martin and I have discussed an idea to introduce a generic helper like
> bpf_get_kern_ctx(void *ctx)
> Given a context, the helper will return a PTR_TO_BTF_ID representing the
> corresponding kernel ctx. So in the above example, user could call
>
> struct bpf_perf_event_data_kern *kctx = bpf_get_kern_ctx(ctx);
> ...
This is an interesting idea!
> To implement bpf_get_kern_ctx helper, the verifier can find the type
> of the context and provide a hidden btf_id as the second parameter of
> the actual kernel helper function like
> bpf_get_kern_ctx(ctx) {
> return ctx;
> }
> /* based on ctx_btf_id, find kctx_btf_id and return it to verifier */
I think we will need a map of ctx_btf_id => kctx_btf_id. Shall we somehow
expose this to the user?
Thanks,
Song
> The bpf_get_kern_ctx helper can be inlined as well.
next prev parent reply other threads:[~2022-11-03 20:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 5:23 [PATCH bpf-next 0/3] bpf: Add bpf_perf_event_read_sample() helper (v1) Namhyung Kim
2022-11-01 5:23 ` [PATCH bpf-next 1/3] perf/core: Prepare sample data before calling BPF Namhyung Kim
2022-11-01 10:03 ` Jiri Olsa
2022-11-04 6:03 ` Namhyung Kim
2022-11-01 5:23 ` [PATCH bpf-next 2/3] bpf: Add bpf_perf_event_read_sample() helper Namhyung Kim
2022-11-01 10:02 ` Jiri Olsa
2022-11-01 18:26 ` Alexei Starovoitov
2022-11-01 18:46 ` Song Liu
2022-11-01 18:52 ` Alexei Starovoitov
2022-11-01 20:04 ` Song Liu
2022-11-01 22:16 ` Namhyung Kim
2022-11-02 0:13 ` Song Liu
2022-11-02 22:18 ` Namhyung Kim
2022-11-03 18:41 ` Song Liu
2022-11-03 19:45 ` Yonghong Song
2022-11-03 20:55 ` Song Liu [this message]
2022-11-03 21:21 ` Yonghong Song
2022-11-04 6:18 ` Namhyung Kim
2022-11-01 5:23 ` [PATCH bpf-next 3/3] bpf: Add perf_event_read_sample test cases Namhyung Kim
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=CF3D88C5-4D62-48E2-97AB-F6A7FF9CEF9D@fb.com \
--to=songliubraving@meta.com \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=yhs@meta.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