From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Ravi Bangoria <ravi.bangoria@amd.com>,
jolsa@kernel.org, irogers@google.com, bp@alien8.de,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION][BISECT] perf/core: Remove pmu linear searching code
Date: Mon, 5 Jun 2023 11:34:00 +0200 [thread overview]
Message-ID: <20230605093400.GK38236@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230605092731.GZ4253@hirez.programming.kicks-ass.net>
On Mon, Jun 05, 2023 at 11:27:31AM +0200, Peter Zijlstra wrote:
> On Mon, Jun 05, 2023 at 08:10:15AM +0100, Mark Rutland wrote:
>
> > How does this work on x86? Do you have pseudo-PMUs for PERF_TYPE_HARDWARE and
> > PERF_TYPE_RAW ?
>
> Generic code maps TYPE_HARDWARE and TYPE_HW_CACHE to TYPE_RAW for a
> first go, only if that fails it will try the actual type.
>
> And x86 has the (first) CPU PMU has TYPE_RAW, on hybrid, it will
> transparently pick the right actual PMU.
Oh, I might've misread that last bit.. TYPE_RAW is always the big core,
it will not magic the thing. If you want little events you gotta
manually find the little pmu.
next prev parent reply other threads:[~2023-06-05 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 11:38 [REGRESSION][BISECT] perf/core: Remove pmu linear searching code Krzysztof Kozlowski
2023-06-05 2:59 ` Ravi Bangoria
2023-06-05 6:16 ` Krzysztof Kozlowski
2023-06-05 3:26 ` Bagas Sanjaya
2023-06-05 7:10 ` Mark Rutland
2023-06-05 9:27 ` Peter Zijlstra
2023-06-05 9:34 ` Peter Zijlstra [this message]
2023-06-05 9:43 ` Ravi Bangoria
2023-06-05 10:14 ` Peter Zijlstra
2023-06-05 10:17 ` Krzysztof Kozlowski
2023-06-05 10:27 ` Mark Rutland
2023-06-06 8:18 ` [tip: perf/core] perf: Re-instate the linear PMU search tip-bot2 for Peter Zijlstra
2023-06-05 9:34 ` [REGRESSION][BISECT] perf/core: Remove pmu linear searching code Ravi Bangoria
2023-06-05 9:54 ` Mark Rutland
2023-06-05 10:03 ` Ravi Bangoria
2023-06-20 12:38 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20230605093400.GK38236@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ravi.bangoria@amd.com \
--cc=regressions@lists.linux.dev \
/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