From: Mark Rutland <mark.rutland@arm.com>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf test hybrid failing on 14700K
Date: Tue, 16 Jan 2024 17:27:23 +0000 [thread overview]
Message-ID: <Zaa8e-fM5rdEwVNp@FVFF77S0Q05N> (raw)
In-Reply-To: <ZaUQaaT_Hi_c0JhO@FVFF77S0Q05N>
On Mon, Jan 15, 2024 at 11:00:57AM +0000, Mark Rutland wrote:
> On Wed, Jan 10, 2024 at 08:29:18AM -0800, Ian Rogers wrote:
> > Lacking hardware with the broken PMU(s) I'm not able to do this. Could
> > you turn the suggestion into a patch and test on BIG.little? I can
> > test on Intel Alderlake.
For the sake of the archive; I sent that out as:
https://lore.kernel.org/lkml/20240116170348.463479-1-mark.rutland@arm.com/
I've given that some testing on big.LITTLE: I've asked Hector and Marc to give
it a go with the Apple M1/M2 PMU specifically.
Mark.
next prev parent reply other threads:[~2024-01-16 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 13:55 perf test hybrid failing on 14700K Arnaldo Carvalho de Melo
2024-01-02 15:43 ` Liang, Kan
2024-01-02 22:41 ` Ian Rogers
2024-01-03 14:15 ` Liang, Kan
2024-01-03 16:31 ` Ian Rogers
2024-01-03 16:28 ` Arnaldo Carvalho de Melo
2024-01-05 12:05 ` Mark Rutland
2024-01-05 17:21 ` Ian Rogers
2024-01-09 16:37 ` Mark Rutland
2024-01-10 16:29 ` Ian Rogers
2024-01-15 11:00 ` Mark Rutland
2024-01-16 17:27 ` Mark Rutland [this message]
2024-01-20 6:09 ` Ian Rogers
2024-01-30 13:56 ` Arnaldo Carvalho de Melo
2024-01-30 14:02 ` Liang, Kan
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=Zaa8e-fM5rdEwVNp@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).