mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, 9 Jan 2024 16:37:18 +0000	[thread overview]
Message-ID: <ZZ12PhUfA_wPAaRR@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <CAP-5=fUK+t1p0g3dKtgyP0g3oixM1G7Xm4BFneY5EMzRW_urdw@mail.gmail.com>

On Fri, Jan 05, 2024 at 09:21:21AM -0800, Ian Rogers wrote:
> While much has been done in the perf tool to work around latent issues
> with ARM's PMU drivers and the behavior changes they have instigated,
> except for 5c816728651a ("arm_pmu: Add PERF_PMU_CAP_EXTENDED_HW_TYPE
> capability") where I wrote the original version, there doesn't seem to
> have been progress made on the ARM PMU driver nor on ARM testing -
> which was why such an issue could exist for so long, across numerous
> Linux releases and ultimately break Hector and Martin.

Ian, which latent issues in the PMU drivers are you referring to?

I already pointed out that one of the problems you have claimed to be a driver
bug is actually due to userspace incorrectly detecting support for the extended
HW type, and I suggested some options which you have so far ignored:

  https://lore.kernel.org/lkml/ZV-CUlQhlkdOzfFZ@FVFF77S0Q05N.cambridge.arm.com/
  https://lore.kernel.org/lkml/ZV-ItX1eMeIdo_00@FVFF77S0Q05N.cambridge.arm.com/

I agree that testing is a problem, and we need to do better from the arm side.

Thanks,
Mark.

  reply	other threads:[~2024-01-09 16:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 13:55 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 [this message]
2024-01-10 16:29           ` Ian Rogers
2024-01-15 11:00             ` Mark Rutland
2024-01-16 17:27               ` Mark Rutland
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=ZZ12PhUfA_wPAaRR@FVFF77S0Q05N.cambridge.arm.com \
    --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
all inboxes | Powered by JetHome®