Re: [PATCH v2 2/2] perf pmu: Improve CPU core PMU HW event list ordering
From: Arnaldo Carvalho de Melo
Date: Mon Aug 03 2020 - 08:54:40 EST
Em Mon, Aug 03, 2020 at 09:00:06AM +0100, John Garry escreveu:
> On 17/06/2020 13:15, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Jun 17, 2020 at 08:31:02PM +0900, Namhyung Kim escreveu:
> > > On Wed, Jun 17, 2020 at 6:06 PM John Garry <john.garry@xxxxxxxxxx> wrote:
> > > > For perf list, the CPU core PMU HW event ordering is such that not all
> > > > events may will be listed adjacent - consider this example:
> > > > cstate_pkg/c6-residency/ [Kernel PMU event]
> > > > cstate_pkg/c7-residency/ [Kernel PMU event]
> > > > Signed-off-by: John Garry <john.garry@xxxxxxxxxx>
> > > Acked-by: Namhyung Kim <namhyung@xxxxxxxxxx>
> > Thanks a lot, applied.
> I'm struggling to understand which branch we should base our development on.
> I don't see these patches in perf/core or linux-next. I saw someone
> mentioned tmp.perf/core as a baseline, but I can't see that branch in
> Please let me know - it would be useful for any dev during the merge window.
So, I'm now pushing things directly to Linus, but just the tooling part,
the branch to do development on is:
At some point I think we'll have a git/perf-tools/perf-tools.git, just
like tip, but for now, please use the one above.
My perf/core in the past was rebaseable, I did changes in it after
publishing, trying to have solid bisectability, since I process patch by
patch doing tests on it when we noticed problems, prior to pushing to
Ingo for tip.
Now I am making perf/core non-rebaseable, I push things there
periodically, tagging what is there with the test results, see:
I'll try and tag today's state of that tree, which I did tests already
but since v5.8 was released, I merged it there and will retest and tag
the test results.
The tmp.perf/core one is an experiment in making what I have in my local
tree available for more bleeding edge things that are being done, say in
that metrics effort, etc, but I think I'll stop that, since, as your
message shows, it is causing confusion.
I did this because these tests take quite some time and sometimes I have
to fix things and restart it, rinse, repeat.
So please use:
I'll further automate all this so that we have a more regular cadence of
updates to perf/core, say every two days or so.
If you have changes that touch both the kernel and userspace, the kernel
bits need to go via tip, the tooling via the perf tree, that for now
(well, it has been like that for quite a long time) is my tree.
Arch specific kernel bits have been going via the arch trees for quite a
while, I think.