All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Chun-Tse Shao <ctshao@google.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	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 2/2] perf evsel: Find process with busy PMUs for EBUSY
Date: Sun, 13 Sep 2026 22:44:43 -0300	[thread overview]
Message-ID: <aqdRi7v_A03mY1tU@x2> (raw)
In-Reply-To: <aihLa9ezNXXZm9mC@x1>

On Tue, Jun 09, 2026 at 02:20:43PM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Jun 09, 2026 at 08:58:03AM -0700, Ian Rogers wrote:
> > On Tue, Jun 2, 2026 at 11:13 AM Chun-Tse Shao <ctshao@google.com> wrote:
> > >
> > > It parses fdinfo with PMU type, comparing with the event which failed to
> > > open, and report the processes causing EBUSY error.
> > >
> > > Testing cycles and intel_pt//
> > >
> > >   $ ./perf stat -e cycles &
> > >   [1] 55569
> > >   $ ./perf stat -e intel_pt// &
> > >   [2] 55683
> > >   $ ./perf stat -e intel_pt//
> > >   Error:
> > >   The PMU intel_pt counters are busy and in use by another process.
> > >   Possible processes:
> > >   55683 ./perf stat -e intel_pt//
> > >
> > > Only perf with intel_pt was reported.
> > >
> > > Reviewed-by: Ian Rogers <irogers@google.com>
> > > Signed-off-by: Chun-Tse Shao <ctshao@google.com>
> > > Assisted-by: Gemini:gemini-3.1-pro-preview
> > 
> > Arnaldo, as the kernel piece of this landed (thanks Peter!) could we
> > land the tool part too?
> 
> Thanks for pointing this out to me, I'll do some housekeeping and
> process this.

I think this hasn't landed, I tried to find the userland part of v8 but
didn't manage to, can you please point it to me?

- Arnaldo

  reply	other threads:[~2026-09-14  1:44 UTC|newest]

Thread overview: 10+ 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-09-14  1:44       ` Arnaldo Carvalho de Melo [this message]
2026-09-14 20:29         ` Chun-Tse Shao
2026-09-15 18:54           ` Ian Rogers
2026-09-15 20:52             ` Chun-Tse Shao
2026-06-04  9:21 ` [PATCH v8 1/2] perf: Reveal PMU type in fdinfo Peter Zijlstra
2026-06-09  8:21 ` [tip: perf/core] " tip-bot2 for Chun-Tse Shao

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=aqdRi7v_A03mY1tU@x2 \
    --to=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=peterz@infradead.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 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.