Linux Perf Users
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
	mark.rutland@arm.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>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [REGRESSION][BISECT] perf/core: Remove pmu linear searching code
Date: Mon, 5 Jun 2023 08:29:53 +0530	[thread overview]
Message-ID: <512e8b06-3ef4-66ae-5ca3-5a863a10c51f@amd.com> (raw)
In-Reply-To: <3abd3693-ad87-9abf-a762-337076638fcc@linaro.org>

On 04-Jun-23 5:08 PM, Krzysztof Kozlowski wrote:
> Hi,
> 
> #regzbot introduced: 9551fbb64d09
> 
> Bisect pointed to commit 9551fbb64d09 ("perf/core: Remove pmu linear
> searching code") as first one where all hardware events are gone from
> perf for ARMv7 Exynos5422 board.

Is this inside KVM guest? Does this help:
https://lore.kernel.org/all/20230525212723.3361524-1-oliver.upton@linux.dev

Thanks,
Ravi

  reply	other threads:[~2023-06-05  3:00 UTC|newest]

Thread overview: 15+ 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 [this message]
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
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-05  9:34   ` 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=512e8b06-3ef4-66ae-5ca3-5a863a10c51f@amd.com \
    --to=ravi.bangoria@amd.com \
    --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=peterz@infradead.org \
    --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