From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Justin He <Justin.He@arm.com>,
John Garry <john.g.garry@oracle.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>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <James.Clark@arm.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
nd <nd@arm.com>
Subject: Re: [PATCH 2/2] perf pmu: Fix num_events calculation
Date: Sat, 11 May 2024 12:52:41 -0300 [thread overview]
Message-ID: <Zj-USRLJIGIvj7iE@x1> (raw)
In-Reply-To: <CAP-5=fULL0KNWA_O0B3r4Q0DA2_FMk=rARhb=z8ySKzFyVwFyw@mail.gmail.com>
On Fri, May 10, 2024 at 05:50:29PM -0700, Ian Rogers wrote:
> On Fri, May 10, 2024 at 1:41 PM Ian Rogers <irogers@google.com> wrote:
> > As such the fix here is incomplete. There may be both sys json events
> > (detected by PMU/id name) and CPU json events (detected by CPUID). I'm
> > looking into a fix.
>
> Patch sent:
> https://lore.kernel.org/lkml/20240511003601.2666907-1-irogers@google.com/
I applied the patch to tmp.perf-tools-next, will go to perf-tools-next
soon, would be good for Justin to test and provide a Tested-by.
- Arnaldo
prev parent reply other threads:[~2024-05-11 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 2:47 [PATCH 0/2] Fix num_events calculation in lazy loading Jia He
2024-05-10 2:47 ` [PATCH 1/2] perf pmu: Allow finishing loading json events when !events_table Jia He
2024-05-10 2:47 ` [PATCH 2/2] perf pmu: Fix num_events calculation Jia He
2024-05-10 6:16 ` Ian Rogers
2024-05-10 6:52 ` Justin He
2024-05-10 20:41 ` Ian Rogers
2024-05-11 0:50 ` Ian Rogers
2024-05-11 15:52 ` 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=Zj-USRLJIGIvj7iE@x1 \
--to=acme@kernel.org \
--cc=James.Clark@arm.com \
--cc=Justin.He@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nd@arm.com \
--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 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.