From: Howard Chu <howardchu95@gmail.com>
To: acme@kernel.org
Cc: mingo@redhat.com, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
peterz@infradead.org, kan.liang@linux.intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Howard Chu <howardchu95@gmail.com>
Subject: [PATCH v1 0/2] perf trace: Enhance task filtering and remove an unused function
Date: Thu, 29 May 2025 23:24:06 -0700 [thread overview]
Message-ID: <20250530062408.1438861-1-howardchu95@gmail.com> (raw)
Task filtering is flawed on perf trace. Spawned threads can't get
augmented, and the BPF program collects more data than it needs. This
patch series adds a pids_targeted BPF map to better filter the tasks,
and makes the bpf-output event '__augmented_syscalls__' system-wide. It
also removes evlist__has_bpf_output() that's no longer useful.
Howard Chu (2):
perf trace: Enhance task filtering
perf evlist: Remove evlist__has_bpf_output()
tools/perf/builtin-trace.c | 52 ++++++++++++++++---
.../bpf_skel/augmented_raw_syscalls.bpf.c | 35 ++++++++++---
tools/perf/util/evlist.c | 14 +----
tools/perf/util/evlist.h | 1 -
4 files changed, 73 insertions(+), 29 deletions(-)
--
2.45.2
next reply other threads:[~2025-05-30 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 6:24 Howard Chu [this message]
2025-05-30 6:24 ` [PATCH v1 1/2] perf trace: Enhance task filtering Howard Chu
2025-05-30 21:30 ` Namhyung Kim
2025-05-30 23:20 ` Howard Chu
2025-05-30 6:24 ` [PATCH v1 2/2] perf evlist: Remove evlist__has_bpf_output() Howard Chu
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=20250530062408.1438861-1-howardchu95@gmail.com \
--to=howardchu95@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--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 \
/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).