From: Tengda Wu <wutengda@huaweicloud.com>
To: Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: song@kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH -next v3 0/2] perf stat: Support inherit events for bperf
Date: Wed, 25 Sep 2024 22:16:16 +0800 [thread overview]
Message-ID: <729eef63-6aed-44db-b18a-eb4bf96aeaab@huaweicloud.com> (raw)
In-Reply-To: <20240916014318.267709-1-wutengda@huaweicloud.com>
Hello,
Sorry for pinging again. Is there any other suggestion with this patch set?
If there is, please let me know.
Thanks,
Tengda
On 2024/9/16 9:43, Tengda Wu wrote:
> Hi,
>
> Here is the 3th version of the series to support inherit events for bperf.
> This version add pid or tgid selection based on filter type in new_task
> prog to avoid memory waste and potential count loss.
>
>
> bperf (perf-stat --bpf-counter) has not supported inherit events
> during fork() since it was first introduced.
>
> This patch series tries to add this support by:
> 1) adding two new bpf programs to monitor task lifecycle;
> 2) recording new tasks in the filter map dynamically;
> 3) reusing `accum_key` of parent task for new tasks.
>
> Thanks,
> Tengda
>
>
> Changelog:
> ---------
> v3: (Address comments from Namhyung, thanks)
> * Use pid or tgid based on filter type in new_task prog
> * Add comments to explain pid usage for TGID type in exit_task prog
>
> v2: https://lore.kernel.org/all/20240905115918.772234-1-wutengda@huaweicloud.com/
> * Remove the unused init_filter_entries in follower bpf, declare
> a global filter_entry_count in bpf_counter instead
> * Attach on_newtask and on_exittask progs only if the filter type
> is either PID or TGID
>
> v1: https://lore.kernel.org/all/20240904123103.732507-1-wutengda@huaweicloud.com/
>
>
> Tengda Wu (2):
> perf stat: Support inherit events during fork() for bperf
> perf test: Use sqrtloop workload to test bperf event
>
> tools/perf/tests/shell/stat_bpf_counters.sh | 2 +-
> tools/perf/util/bpf_counter.c | 32 +++++--
> tools/perf/util/bpf_skel/bperf_follower.bpf.c | 87 +++++++++++++++++--
> tools/perf/util/bpf_skel/bperf_u.h | 5 ++
> 4 files changed, 112 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2024-09-25 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 1:43 [PATCH -next v3 0/2] perf stat: Support inherit events for bperf Tengda Wu
2024-09-16 1:43 ` [PATCH -next v3 1/2] perf stat: Support inherit events during fork() " Tengda Wu
2024-10-09 17:18 ` Song Liu
2024-10-10 0:31 ` Namhyung Kim
2024-10-10 4:53 ` Tengda Wu
2024-10-11 3:07 ` Tengda Wu
2024-10-11 3:21 ` Song Liu
2024-09-16 1:43 ` [PATCH -next v3 2/2] perf test: Use sqrtloop workload to test bperf event Tengda Wu
2024-09-25 14:16 ` Tengda Wu [this message]
2024-09-26 3:43 ` [PATCH -next v3 0/2] perf stat: Support inherit events for bperf Namhyung Kim
2024-10-09 5:21 ` Namhyung Kim
2024-10-09 17:21 ` Song Liu
2024-10-10 0:22 ` 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=729eef63-6aed-44db-b18a-eb4bf96aeaab@huaweicloud.com \
--to=wutengda@huaweicloud.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).