From: Will Deacon <will@kernel.org>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/2] perf/dwc_pcie: Fix the swapped event numbers as well as the documentation
Date: Mon, 9 Dec 2024 18:43:03 +0000 [thread overview]
Message-ID: <173375912254.1125785.1872820731502163004.b4-ty@kernel.org> (raw)
In-Reply-To: <20241205061914.5568-1-ilkka@os.amperecomputing.com>
On Thu, 05 Dec 2024 06:19:12 +0000, Ilkka Koskinen wrote:
> According to the versions of Designware Cores PCI Express Controller Databook
> I found, the eventid for "L1 aux" is 0x08 and "TX L0s and RX L0S" is 0x09.
>
> Shuai and Jing, could you verify that your document matches ours and the events
> are indeed swapped in the driver at the moment?
>
> Cheers, Ilkka
>
> [...]
Applied to will (for-next/perf), thanks!
[1/2] perf/dwc_pcie: Fix the event numbers
https://git.kernel.org/will/c/e64c22cc2e61
[2/2] Documentation: dwc_pcie_pmu: Fix the mnemonics and eventid
https://git.kernel.org/will/c/8632306e093c
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-12-09 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 6:19 Ilkka Koskinen
2024-12-05 6:19 ` [PATCH 1/2] perf/dwc_pcie: Fix the event numbers Ilkka Koskinen
2024-12-05 7:25 ` Shuai Xue
2024-12-05 6:19 ` [PATCH 2/2] Documentation: dwc_pcie_pmu: Fix the mnemonics and eventid Ilkka Koskinen
2024-12-05 7:26 ` Shuai Xue
2024-12-05 7:24 ` [PATCH 0/2] perf/dwc_pcie: Fix the swapped event numbers as well as the documentation Shuai Xue
2024-12-09 18:43 ` 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=173375912254.1125785.1872820731502163004.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=ilkka@os.amperecomputing.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=xueshuai@linux.alibaba.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
all inboxes | Powered by JetHome®