From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Wang, Weilin" <weilin.wang@intel.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] perf intel-tpebs: Filter non-workload samples
Date: Fri, 16 May 2025 11:35:29 -0300 [thread overview]
Message-ID: <aCdNMenCaonhRfJK@x1> (raw)
In-Reply-To: <CO6PR11MB5635C6FF9A6C91B68FCE7937EE90A@CO6PR11MB5635.namprd11.prod.outlook.com>
On Thu, May 15, 2025 at 08:46:22PM +0000, Wang, Weilin wrote:
> > -----Original Message-----
> > From: Ian Rogers <irogers@google.com>
> > Sent: Wednesday, April 30, 2025 1:01 PM
> > To: Peter Zijlstra <peterz@infradead.org>; Ingo Molnar <mingo@redhat.com>;
> > Arnaldo Carvalho de Melo <acme@kernel.org>; Namhyung Kim
> > <namhyung@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>; Hunter, Adrian
> > <adrian.hunter@intel.com>; Kan Liang <kan.liang@linux.intel.com>; Wang,
> > Weilin <weilin.wang@intel.com>; James Clark <james.clark@linaro.org>; linux-
> > perf-users@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: [PATCH v1] perf intel-tpebs: Filter non-workload samples
> >
> > If perf is running with a benchmark then we want the retirement
> > latency samples associated with the benchmark rather than from the
> > system as a whole. Use the workload's PID to filter out samples that
> > aren't from the workload or its children.
> >
> > Signed-off-by: Ian Rogers <irogers@google.com>
> Tested-by: Weilin Wang <weilin.wang@intel.com>
Thanks, applied to perf-tools-next,
- Arnaldo
> > ---
> > tools/perf/util/intel-tpebs.c | 59
> > ++++++++++++++++++++++++++++++++++-
> > 1 file changed, 58 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/util/intel-tpebs.c b/tools/perf/util/intel-tpebs.c
> > index 7fd6cae1063e..4ad4bc118ea5 100644
> > --- a/tools/perf/util/intel-tpebs.c
> > +++ b/tools/perf/util/intel-tpebs.c
> > @@ -3,7 +3,7 @@
> > * intel_tpebs.c: Intel TPEBS support
> > */
> >
> > -
> > +#include <api/fs/fs.h>
> > #include <sys/param.h>
> > #include <subcmd/run-command.h>
> > #include <thread.h>
> > @@ -121,6 +121,59 @@ static int evsel__tpebs_start_perf_record(struct
> > evsel *evsel)
> > return ret;
> > }
> >
> > +static bool is_child_pid(pid_t parent, pid_t child)
> > +{
> > + if (parent < 0 || child < 0)
> > + return false;
> > +
> > + while (true) {
> > + char path[PATH_MAX];
> > + char line[256];
> > + FILE *fp;
> > +
> > +new_child:
> > + if (parent == child)
> > + return true;
> > +
> > + if (child <= 0)
> > + return false;
> > +
> > + scnprintf(path, sizeof(path), "%s/%d/status",
> > procfs__mountpoint(), child);
> > + fp = fopen(path, "r");
> > + if (!fp) {
> > + /* Presumably the process went away. Assume not a
> > child. */
> > + return false;
> > + }
> > + while (fgets(line, sizeof(line), fp) != NULL) {
> > + if (strncmp(line, "PPid:", 5) == 0) {
> > + fclose(fp);
> > + if (sscanf(line + 5, "%d", &child) != 1) {
> > + /* Unexpected error parsing. */
> > + return false;
> > + }
> > + goto new_child;
> > + }
> > + }
> > + /* Unexpected EOF. */
> > + fclose(fp);
> > + return false;
> > + }
> > +}
> > +
> > +static bool should_ignore_sample(const struct perf_sample *sample, const
> > struct tpebs_retire_lat *t)
> > +{
> > + pid_t workload_pid = t->evsel->evlist->workload.pid;
> > + pid_t sample_pid = sample->pid;
> > +
> > + if (workload_pid < 0 || workload_pid == sample_pid)
> > + return false;
> > +
> > + if (!t->evsel->core.attr.inherit)
> > + return true;
> > +
> > + return !is_child_pid(workload_pid, sample_pid);
> > +}
> > +
> > static int process_sample_event(const struct perf_tool *tool
> > __maybe_unused,
> > union perf_event *event __maybe_unused,
> > struct perf_sample *sample,
> > @@ -140,6 +193,10 @@ static int process_sample_event(const struct
> > perf_tool *tool __maybe_unused,
> > mutex_unlock(tpebs_mtx_get());
> > return -EINVAL;
> > }
> > + if (should_ignore_sample(sample, t)) {
> > + mutex_unlock(tpebs_mtx_get());
> > + return 0;
> > + }
> > /*
> > * Need to handle per core results? We are assuming average retire
> > * latency value will be used. Save the number of samples and the sum
> > of
> > --
> > 2.49.0.906.g1f30a19c02-goog
>
prev parent reply other threads:[~2025-05-16 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:01 [PATCH v1] perf intel-tpebs: Filter non-workload samples Ian Rogers
2025-05-15 20:46 ` Wang, Weilin
2025-05-16 14:35 ` Arnaldo Carvalho de Melo [this message]
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=aCdNMenCaonhRfJK@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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=weilin.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.