From: Peter Zijlstra <peterz@infradead.org>
To: Dmitrii Dolgov <9erthalion6@gmail.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
songliubraving@fb.com, rostedt@goodmis.org, mingo@redhat.com,
mhiramat@kernel.org, alexei.starovoitov@gmail.com
Subject: Re: [PATCH v4 1/1] perf/kprobe: maxactive for fd-based kprobe
Date: Thu, 14 Jul 2022 21:57:48 +0200 [thread overview]
Message-ID: <YtB1PK+NUF5RL9Er@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20220714193403.13211-1-9erthalion6@gmail.com>
On Thu, Jul 14, 2022 at 09:34:03PM +0200, Dmitrii Dolgov wrote:
> From: Song Liu <songliubraving@fb.com>
>
> Enable specifying maxactive for fd based kretprobe. This will be useful
> for tracing tools like bcc and bpftrace (see for example discussion [1]).
> Use highest 4 bit (bit 59-63) to allow specifying maxactive by log2.
What's maxactive? This doesn't really tell me much. Why are the top 4
bits the best to use?
>
> The original patch [2] seems to be fallen through the cracks and wasn't
> applied. I've merely rebased the work done by Song Liu, verififed it
> still works, and modified to allow specifying maxactive by log2 per
> suggestion from the discussion thread.
That just doesn't belong in a Changelog.
>
> Note that changes in rethook implementation may render maxactive
> obsolete.
Then why bother creating an ABI for it?
>
> [1]: https://github.com/iovisor/bpftrace/issues/835
> [2]: https://lore.kernel.org/all/20191007223111.1142454-1-songliubraving@fb.com/
>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> Signed-off-by: Dmitrii Dolgov <9erthalion6@gmail.com>
> Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Lots of question and not a single answer in sight...
next prev parent reply other threads:[~2022-07-14 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 19:34 [PATCH v4 1/1] perf/kprobe: maxactive for fd-based kprobe Dmitrii Dolgov
2022-07-14 19:42 ` Steven Rostedt
2022-07-14 19:57 ` Peter Zijlstra [this message]
2022-07-15 9:52 ` Dmitry Dolgov
2022-07-20 14:07 ` Peter Zijlstra
2022-07-24 10:36 ` Dmitry Dolgov
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=YtB1PK+NUF5RL9Er@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=9erthalion6@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=songliubraving@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