From: Will Deacon <will@kernel.org>
To: mark.rutland@arm.com, namhyung@kernel.org,
linux-arm-kernel@lists.infradead.org, acme@kernel.org,
peterz@infradead.org, linux-kernel@vger.kernel.org,
alexander.shishkin@linux.intel.com, suzuki.poulose@arm.com,
mingo@redhat.com, jolsa@redhat.com,
Yang Jihong <yangjihong1@huawei.com>,
linux@armlinux.org.uk, julien.thierry.kdev@gmail.com
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm_pmu: Fix write counter incorrect in ARMv7 big-endian mode
Date: Tue, 1 Jun 2021 19:21:05 +0100 [thread overview]
Message-ID: <162255342222.565985.6841867867771052763.b4-ty@kernel.org> (raw)
In-Reply-To: <20210430012659.232110-1-yangjihong1@huawei.com>
On Fri, 30 Apr 2021 09:26:59 +0800, Yang Jihong wrote:
> Commit 3a95200d3f89a ("arm_pmu: Change API to support 64bit counter values")
> changes the input "value" type from 32-bit to 64-bit,
> which introduces the following problem:
> ARMv7 PMU counters is 32-bit width, in big-endian mode, write counter uses
> high 32-bit, which writes an incorrect value.
>
> Before:
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] arm_pmu: Fix write counter incorrect in ARMv7 big-endian mode
https://git.kernel.org/will/c/fdbef8c4e68a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-01 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 1:26 [PATCH] arm_pmu: Fix write counter incorrect in ARMv7 big-endian mode Yang Jihong
2021-04-30 12:34 ` Mark Rutland
2021-05-20 8:31 ` Yang Jihong
2021-06-01 18:21 ` Will Deacon [this message]
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=162255342222.565985.6841867867771052763.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=jolsa@redhat.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=yangjihong1@huawei.com \
/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