BPF List
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>, Song Liu <songliubraving@fb.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>, Martin Lau <kafai@fb.com>,
	Yonghong Song <yhs@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next] bpf: Add bpf_read_raw_record() helper
Date: Tue, 23 Aug 2022 22:32:23 -0700	[thread overview]
Message-ID: <6305b7e7c7709_6d4fc20869@john.notmuch> (raw)
In-Reply-To: <CAM9d7cgxP6+R2BkVZfRAVvFUaJcknu8wAvKa_b1TBnTdKKiQvw@mail.gmail.com>

Namhyung Kim wrote:
> Hi Song,
> 
> On Tue, Aug 23, 2022 at 3:19 PM Song Liu <songliubraving@fb.com> wrote:
> >
> >
> >
> > > On Aug 23, 2022, at 2:03 PM, Namhyung Kim <namhyung@kernel.org> wrote:
> > >
> > > The helper is for BPF programs attached to perf_event in order to read
> > > event-specific raw data.  I followed the convention of the
> > > bpf_read_branch_records() helper so that it can tell the size of
> > > record using BPF_F_GET_RAW_RECORD flag.
> > >
> > > The use case is to filter perf event samples based on the HW provided
> > > data which have more detailed information about the sample.
> > >
> > > Note that it only reads the first fragment of the raw record.  But it
> > > seems mostly ok since all the existing PMU raw data have only single
> > > fragment and the multi-fragment records are only for BPF output attached
> > > to sockets.  So unless it's used with such an extreme case, it'd work
> > > for most of tracing use cases.
> > >
> > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > > ---
> > > I don't know how to test this.  As the raw data is available on some
> > > hardware PMU only (e.g. AMD IBS).  I tried a tracepoint event but it was
> > > rejected by the verifier.  Actually it needs a bpf_perf_event_data
> > > context so that's not an option IIUC.
> >
> > Can we add a software event that generates raw data for testing?
> 
> Ok, now I think that I can use a bpf-output sw event.  It would need
> another BPF program to write data to the event and the test program
> can read it from BPF using this helper. :)
> 
> Thanks,
> Namhyung

Ah good idea. Feel free to carry my ACK to the v2 with the test.

  reply	other threads:[~2022-08-24  5:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 21:03 [PATCH bpf-next] bpf: Add bpf_read_raw_record() helper Namhyung Kim
2022-08-23 22:19 ` Song Liu
2022-08-23 22:45   ` Namhyung Kim
2022-08-24  5:32     ` John Fastabend [this message]
2022-08-25 16:57       ` Namhyung Kim
2022-08-25 17:04         ` Song Liu
2022-08-25 17:21           ` Namhyung Kim
2022-08-24  5:31 ` John Fastabend
2022-08-24  6:09   ` Namhyung Kim
2022-08-25 21:33 ` Andrii Nakryiko
2022-08-25 22:08   ` Song Liu
2022-08-25 23:03     ` Andrii Nakryiko
2022-08-26  2:35       ` Song Liu
2022-08-26  5:22         ` Namhyung Kim
2022-08-26  5:53           ` Song Liu
2022-08-26 16:33             ` Namhyung Kim
2022-08-26 18:09               ` Song Liu
2022-08-26 18:44                 ` Song Liu
2022-08-26 19:30                   ` Namhyung Kim
2022-08-26 20:58                     ` Song Liu
2022-08-26 21:12                       ` Namhyung Kim
2022-08-26 21:25                         ` Song Liu
2022-08-27  6:25                           ` Namhyung Kim
2022-08-29  7:20                             ` Song Liu
2022-08-29 20:11                               ` Namhyung Kim
2022-08-26 19:21                 ` Namhyung Kim
2022-08-26 20:52                   ` Song Liu
2022-08-25 22:13   ` Namhyung Kim
2022-08-25 23:09     ` Andrii Nakryiko

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=6305b7e7c7709_6d4fc20869@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sdf@google.com \
    --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