From: Jiri Olsa <olsajiri@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <olsajiri@gmail.com>, Tao Chen <chen.dylane@linux.dev>,
andrii@kernel.org, eddyz87@gmail.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH bpf-next] libbpf: remove sample_period init in perf_buffer
Date: Wed, 23 Apr 2025 17:51:08 +0200 [thread overview]
Message-ID: <aAkMbBdzWX_iE1zM@krava> (raw)
In-Reply-To: <aAfok3ha8QQkP8VB@google.com>
On Tue, Apr 22, 2025 at 12:05:55PM -0700, Namhyung Kim wrote:
> Hello,
>
> On Tue, Apr 22, 2025 at 03:43:43PM +0200, Jiri Olsa wrote:
> > On Tue, Apr 22, 2025 at 05:15:58PM +0800, Tao Chen wrote:
> > > It seems that sample_period no used in perf buffer, actually only
> > > wakeup_events valid about events aggregation for wakeup. So remove
> > > it to avoid causing confusion.
> >
> > I don't see too much confusion in keeping it, but I think it
> > should be safe to remove it
> >
> > PERF_COUNT_SW_BPF_OUTPUT is "trigered" by bpf_perf_event_output,
> > AFAICS there's no path checking on sample_period for this event
> > used in context of perf_buffer__new, Namhyung, thoughts?
>
> It seems to be ok to call mmap(2) for non-sampling events.
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Tao Chen,
could you please resend without rfc tag? plz keeps acks
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
>
> Thanks,
> Namhyung
>
> >
> > >
> > > Fixes: fb84b8224655 ("libbpf: add perf buffer API")
> > > Signed-off-by: Tao Chen <chen.dylane@linux.dev>
> > > ---
> > > tools/lib/bpf/libbpf.c | 1 -
> > > 1 file changed, 1 deletion(-)
> > >
> > > diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> > > index 194809da5172..1830e3c011a5 100644
> > > --- a/tools/lib/bpf/libbpf.c
> > > +++ b/tools/lib/bpf/libbpf.c
> > > @@ -13306,7 +13306,6 @@ struct perf_buffer *perf_buffer__new(int map_fd, size_t page_cnt,
> > > attr.config = PERF_COUNT_SW_BPF_OUTPUT;
> > > attr.type = PERF_TYPE_SOFTWARE;
> > > attr.sample_type = PERF_SAMPLE_RAW;
> > > - attr.sample_period = sample_period;
> > > attr.wakeup_events = sample_period;
> > >
> > > p.attr = &attr;
> > > --
> > > 2.43.0
> > >
next prev parent reply other threads:[~2025-04-23 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 9:15 [RFC PATCH bpf-next] libbpf: remove sample_period init in perf_buffer Tao Chen
2025-04-22 13:43 ` Jiri Olsa
2025-04-22 19:05 ` Namhyung Kim
2025-04-23 15:51 ` Jiri Olsa [this message]
2025-04-23 16:26 ` Tao Chen
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=aAkMbBdzWX_iE1zM@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=namhyung@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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