mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
	Jing Zhang <renyu.zj@linux.alibaba.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: 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: Thu, 5 Dec 2024 15:24:04 +0800	[thread overview]
Message-ID: <412549fa-ca7a-42a1-9fad-85d3dcd14b79@linux.alibaba.com> (raw)
In-Reply-To: <20241205061914.5568-1-ilkka@os.amperecomputing.com>



在 2024/12/5 14:19, Ilkka Koskinen 写道:
> 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?

Yep, it is a typo.

> 
> Cheers, Ilkka

Thanks for the fixes :)

Best Regards,
Shuai

> 
> 
> 
> Ilkka Koskinen (2):
>    perf/dwc_pcie: Fix the event numbers
>    Documentation: dwc_pcie_pmu: Fix the mnemonics and eventid
> 
>   Documentation/admin-guide/perf/dwc_pcie_pmu.rst | 6 +++---
>   drivers/perf/dwc_pcie_pmu.c                     | 4 ++--
>   2 files changed, 5 insertions(+), 5 deletions(-)
> 


  parent reply	other threads:[~2024-12-05  7:24 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 ` Shuai Xue [this message]
2024-12-09 18:43 ` [PATCH 0/2] perf/dwc_pcie: Fix the swapped event numbers as well as the documentation Will Deacon

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=412549fa-ca7a-42a1-9fad-85d3dcd14b79@linux.alibaba.com \
    --to=xueshuai@linux.alibaba.com \
    --cc=corbet@lwn.net \
    --cc=ilkka@os.amperecomputing.com \
    --cc=jonathan.cameron@huawei.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=will@kernel.org \
    /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®