Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Will Deacon <will@kernel.org>
To:     Peter Newman <peternewman@google.com>
Cc:     catalin.marinas@arm.com, kernel-team@android.com,
        Will Deacon <will@kernel.org>, linux-kernel@vger.kernel.org,
        jolsa@kernel.org, alexander.shishkin@linux.intel.com,
        irogers@google.com, peterz@infradead.org, mark.rutland@arm.com,
        acme@kernel.org, eranian@google.com, adrian.hunter@intel.com,
        linux-arm-kernel@lists.infradead.org, namhyung@kernel.org,
        linux-perf-users@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH v6] arm64: pmuv3: dynamically map PERF_COUNT_HW_BRANCH_INSTRUCTIONS
Date:   Tue, 11 Apr 2023 14:04:35 +0100
Message-Id: <168121292090.358997.14432007488088025550.b4-ty@kernel.org>
In-Reply-To: <20230411093809.657501-1-peternewman@google.com>
References: <20230411093809.657501-1-peternewman@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 11 Apr 2023 11:38:09 +0200, Peter Newman wrote:
> From: Stephane Eranian <eranian@google.com>
> 
> The mapping of perf_events generic hardware events to actual PMU events on
> ARM PMUv3 may not always be correct. This is in particular true for the
> PERF_COUNT_HW_BRANCH_INSTRUCTIONS event. Although the mapping points to an
> architected event, it may not always be available. This can be seen with a
> simple:
> 
> [...]

Applied to will (for-next/perf), thanks!

[1/1] arm64: pmuv3: dynamically map PERF_COUNT_HW_BRANCH_INSTRUCTIONS
      https://git.kernel.org/will/c/a30b87e6bd7d

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev