[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP-5=fX1XwUrnzrxGgQLK2J46jjsCUq8egbV_9p0eNiVD7-EbQ@mail.gmail.com>
Date: Sun, 26 May 2024 08:20:28 -0700
From: Ian Rogers <irogers@...gle.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Leo Yan <leo.yan@...ux.dev>,
Namhyung Kim <namhyung@...nel.org>, Mark Rutland <mark.rutland@....com>,
Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, Clark Williams <williams@...hat.com>,
Kate Carcia <kcarcia@...hat.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, Anne Macedo <retpolanne@...teo.net>,
Bhaskar Chowdhury <unixbhaskar@...il.com>, Ethan Adams <j.ethan.adams@...il.com>,
James Clark <james.clark@....com>, Kan Liang <kan.liang@...ux.intel.com>,
Thomas Richter <tmricht@...ux.ibm.com>, Tycho Andersen <tycho@...ho.pizza>,
Yang Jihong <yangjihong@...edance.com>
Subject: Re: [GIT PULL] perf tools changes for v6.10
On Sun, May 26, 2024 at 4:10 AM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
> Ian's has been working on this for long time, testing all this takes a
> lot of time and requires access to lots of hardware not easily available
> for all of us, so its bound to break here and there, what we do when
> this happens depends on when the problem is detected, and today Linus is
> expected to close the merge window, so a revert is the technical, if not
> pleasant thing to do now.
Agreed. I think the only other option is:
https://lore.kernel.org/lkml/20240525152927.665498-1-irogers@google.com/
and then when specifying the CPU cycles event on these Ampere systems
you have to do:
$ perf record -e 'armv8_pmuv3_0/cycles/P' ...
but Linus isn't happy with having to specify a PMU like that. As that
is an ARM/Ampere only problem I'm not sure it is so bad.
Thanks,
Ian
> - Arnaldo
Powered by blists - more mailing lists