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,
gautam@linux.ibm.com, Howard Chu <howardchu95@gmail.com>,
James Clark <james.clark@linaro.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH v16 01/10] perf evsel: Expose evsel__is_offcpu_event() for future use
Date: Wed, 30 Apr 2025 19:27:59 -0700 [thread overview]
Message-ID: <20250501022809.449767-2-howardchu95@gmail.com> (raw)
In-Reply-To: <20250501022809.449767-1-howardchu95@gmail.com>
Expose evsel__is_offcpu_event() so it can be used in
off_cpu_config(), evsel__parse_sample(), and perf script.
Tested-by: Gautam Menghani <gautam@linux.ibm.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Reviewed-by: Ian Rogers <irogers@google.com>
Signed-off-by: Howard Chu <howardchu95@gmail.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: James Clark <james.clark@linaro.org>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lore.kernel.org/r/20241108204137.2444151-3-howardchu95@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/util/evsel.c | 2 +-
tools/perf/util/evsel.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index 1d79ffecd41f..2559943d199e 100644
--- a/tools/perf/util/evsel.c
+++ b/tools/perf/util/evsel.c
@@ -1275,7 +1275,7 @@ static void evsel__set_default_freq_period(struct record_opts *opts,
}
}
-static bool evsel__is_offcpu_event(struct evsel *evsel)
+bool evsel__is_offcpu_event(struct evsel *evsel)
{
return evsel__is_bpf_output(evsel) && evsel__name_is(evsel, OFFCPU_EVENT);
}
diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
index 42dcadfef8ce..3d47d9318d92 100644
--- a/tools/perf/util/evsel.h
+++ b/tools/perf/util/evsel.h
@@ -563,4 +563,6 @@ u64 evsel__bitfield_swap_branch_flags(u64 value);
void evsel__set_config_if_unset(struct perf_pmu *pmu, struct evsel *evsel,
const char *config_name, u64 val);
+bool evsel__is_offcpu_event(struct evsel *evsel);
+
#endif /* __PERF_EVSEL_H */
--
2.45.2
next prev parent reply other threads:[~2025-05-01 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 2:27 [PATCH v16 00/10] perf record --off-cpu: Dump off-cpu samples directly Howard Chu
2025-05-01 2:27 ` Howard Chu [this message]
2025-05-01 2:28 ` [PATCH v16 02/10] perf record --off-cpu: Parse off-cpu event Howard Chu
2025-05-01 2:28 ` [PATCH v16 03/10] perf record --off-cpu: Preparation of off-cpu BPF program Howard Chu
2025-05-01 2:28 ` [PATCH v16 04/10] perf record --off-cpu: Dump off-cpu samples in BPF Howard Chu
2025-05-01 2:28 ` [PATCH v16 05/10] perf evsel: Assemble offcpu samples Howard Chu
2025-05-01 2:28 ` [PATCH v16 06/10] perf record --off-cpu: Disable perf_event's callchain collection Howard Chu
2025-05-01 2:28 ` [PATCH v16 07/10] perf script: Display off-cpu samples correctly Howard Chu
2025-05-01 2:28 ` [PATCH v16 08/10] perf record --off-cpu: Dump the remaining samples in BPF's stack trace map Howard Chu
2025-05-01 2:28 ` [PATCH v16 09/10] perf record --off-cpu: Add --off-cpu-thresh option Howard Chu
2025-05-01 2:28 ` [PATCH v16 10/10] perf test: Add direct off-cpu tests Howard Chu
2025-05-01 15:13 ` [PATCH v16 00/10] perf record --off-cpu: Dump off-cpu samples directly Ian Rogers
2025-05-05 15:56 ` Arnaldo Carvalho de Melo
2025-05-06 19:48 ` Ian Rogers
[not found] ` <CA+JHD93FaugH5ny6+bBkciwoWzLN5RKCbtBq77V2bi8Rs15-UQ@mail.gmail.com>
2025-05-06 20:51 ` Ian Rogers
[not found] ` <CA+JHD935y5ky0EWrG4okShjizP9JDp1hOoUiCNT3c6WUj0k1VA@mail.gmail.com>
2025-05-14 20:15 ` Howard Chu
2025-05-15 18:20 ` 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=20250501022809.449767-2-howardchu95@gmail.com \
--to=howardchu95@gmail.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=gautam@linux.ibm.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 \
/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).