From: Song Liu <songliubraving@fb.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: John Fastabend <john.fastabend@gmail.com>,
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>, 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: Thu, 25 Aug 2022 17:04:50 +0000 [thread overview]
Message-ID: <E6872BF2-8DB9-4D42-957B-E57EAE28AA65@fb.com> (raw)
In-Reply-To: <CAM9d7chYaeHvEkq2zCKeA6FiO0wfC2LCGc-1Sj=KdS8oU-2iFw@mail.gmail.com>
> On Aug 25, 2022, at 9:57 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Tue, Aug 23, 2022 at 10:32 PM John Fastabend
> <john.fastabend@gmail.com> wrote:
>> Namhyung Kim wrote:
>>> 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. :)
>>
>> Ah good idea. Feel free to carry my ACK to the v2 with the test.
>
> Hmm.. it seems not to work because
> 1. bpf_output sw event doesn't have the overflow mechanism and it
> doesn't call the bpf program.
> 2. even if I added it, it couldn't run due to the recursion protection by
> bpf_prog_active.
How about we enable some raw record for a software event? Something not
controlled by BPF?
If this doesn't work, a self test that only runs on some hardware is also
helpful.
Thanks,
Song
next prev parent reply other threads:[~2022-08-25 17:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 21:03 Namhyung Kim
2022-08-23 22:19 ` Song Liu
2022-08-23 22:45 ` Namhyung Kim
2022-08-24 5:32 ` John Fastabend
2022-08-25 16:57 ` Namhyung Kim
2022-08-25 17:04 ` Song Liu [this message]
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=E6872BF2-8DB9-4D42-957B-E57EAE28AA65@fb.com \
--to=songliubraving@fb.com \
--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=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=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
all inboxes | Powered by JetHome®