From: Peter Zijlstra <peterz@infradead.org>
To: Chun-Tse Shao <ctshao@google.com>
Cc: Ian Rogers <irogers@google.com>, 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>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Thomas Falcon <thomas.falcon@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v8 1/2] perf: Reveal PMU type in fdinfo
Date: Thu, 4 Jun 2026 11:21:40 +0200 [thread overview]
Message-ID: <20260604092140.GE3126523@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260602181349.3969429-1-ctshao@google.com>
On Tue, Jun 02, 2026 at 11:13:48AM -0700, Chun-Tse Shao wrote:
> It gives useful info on knowing which PMUs are reserved by this process.
> Also add config which would be useful.
> Testing cycles:
>
> $ ./perf stat -e cycles &
> $ cat /proc/`pidof perf`/fdinfo/3
> pos: 0
> flags: 02000002
> mnt_id: 16
> ino: 3081
> perf_event_attr.type: 0
> perf_event_attr.config: 0x0
> perf_event_attr.config1: 0x0
> perf_event_attr.config2: 0x0
> perf_event_attr.config3: 0x0
> perf_event_attr.config4: 0x0
>
> Testing L1-dcache-load-misses:
>
> $ ./perf stat -e L1-dcache-load-misses &
> $ cat /proc/`pidof perf`/fdinfo/3
> pos: 0
> flags: 02000002
> mnt_id: 16
> ino: 1072
> perf_event_attr.type: 3
> perf_event_attr.config: 0x10000
> perf_event_attr.config1: 0x0
> perf_event_attr.config2: 0x0
> perf_event_attr.config3: 0x0
> perf_event_attr.config4: 0x0
>
> Reviewed-by: Ian Rogers <irogers@google.com>
> Signed-off-by: Chun-Tse Shao <ctshao@google.com>
> Assisted-by: Gemini:gemini-3.1-pro-preview
> ---
Yeah, I suppose I'll take this. But I'm not sure about the wording here.
PMUs aren't really reserved as such.
prev parent reply other threads:[~2026-06-04 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 18:13 [PATCH v8 1/2] perf: Reveal PMU type in fdinfo Chun-Tse Shao
2026-06-02 18:13 ` [PATCH v8 2/2] perf evsel: Find process with busy PMUs for EBUSY Chun-Tse Shao
2026-06-09 15:58 ` Ian Rogers
2026-06-09 17:20 ` Arnaldo Carvalho de Melo
2026-06-04 9:21 ` Peter Zijlstra [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=20260604092140.GE3126523@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--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=thomas.falcon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox