From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Yicong Yang <yangyicong@huawei.com>
Cc: <will@kernel.org>, <mark.rutland@arm.com>, <hejunhao3@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <yangyicong@hisilicon.com>,
<linuxarm@huawei.com>, <prime.zeng@hisilicon.com>,
<fanghao11@huawei.com>
Subject: Re: [PATCH v2 5/8] drivers/perf: hisi_pcie: Check the target filter properly
Date: Mon, 26 Feb 2024 15:14:42 +0000 [thread overview]
Message-ID: <20240226151442.000053ad@Huawei.com> (raw)
In-Reply-To: <20240223103359.18669-6-yangyicong@huawei.com>
On Fri, 23 Feb 2024 18:33:56 +0800
Yicong Yang <yangyicong@huawei.com> wrote:
> From: Junhao He <hejunhao3@huawei.com>
>
> The PMU can monitor traffic of certain target Root Port or downstream
> target Endpoint. User can specify the target filter by the "port" or
> "bdf" option respectively. The PMU can only monitor the Root Port or
> Endpoint on the same PCIe core so the value of "port" or "bdf" should
> be valid and will be checked by the driver.
>
> Currently at least and only one of "port" and "bdf" option must be set.
> If "port" filter is not set or is set explicitly to zero (default),
> driver will regard the user specifies a "bdf" option since "port" option
> is a bitmask of the target Root Ports and zero is not a valid
> value.
>
> If user not explicitly set "port" or "bdf" filter, the driver uses "bdf"
> default value (zero) to set target filter, but driver will skip the
> check of bdf=0, although it's a valid value (meaning 0000:000:00.0).
> Then the user just gets zero.
>
> Therefore, we need to check if both "port" and "bdf" are invalid, then
> return failure and report warning.
>
> Testing:
> before the patch:
> 0 hisi_pcie0_core1/rx_mrd_flux/
> 0 hisi_pcie0_core1/rx_mrd_flux,port=0/
> 24,124 hisi_pcie0_core1/rx_mrd_flux,port=1/
> 0 hisi_pcie0_core1/rx_mrd_flux,bdf=0/
> 0 hisi_pcie0_core1/rx_mrd_flux,port=0x800/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,bdf=1/
> 24,132 hisi_pcie0_core1/rx_mrd_flux,bdf=0x1700/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x0/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x1/
> 24,138 hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x1700/
> 24,126 hisi_pcie0_core1/rx_mrd_flux,port=0x1,bdf=0x0/
>
> after the patch:
> <not supported> hisi_pcie0_core1/rx_mrd_flux/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,port=0/
> 24,153 hisi_pcie0_core1/rx_mrd_flux,port=1/
> 0 hisi_pcie0_core1/rx_mrd_flux,port=0x800/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,bdf=0/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,bdf=1/
> 24,117 hisi_pcie0_core1/rx_mrd_flux,bdf=0x1700/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x0/
> <not supported> hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x1/
> 24,120 hisi_pcie0_core1/rx_mrd_flux,port=0x0,bdf=0x1700/
> 24,123 hisi_pcie0_core1/rx_mrd_flux,port=0x1,bdf=0x0/
>
> Signed-off-by: Junhao He <hejunhao3@huawei.com>
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
Thanks for explanation on v1. I'm fine with this now.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> drivers/perf/hisilicon/hisi_pcie_pmu.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/perf/hisilicon/hisi_pcie_pmu.c b/drivers/perf/hisilicon/hisi_pcie_pmu.c
> index 6f39cb82661e..b2dde7559639 100644
> --- a/drivers/perf/hisilicon/hisi_pcie_pmu.c
> +++ b/drivers/perf/hisilicon/hisi_pcie_pmu.c
> @@ -306,10 +306,10 @@ static bool hisi_pcie_pmu_valid_filter(struct perf_event *event,
> if (hisi_pcie_get_trig_len(event) > HISI_PCIE_TRIG_MAX_VAL)
> return false;
>
> - if (requester_id) {
> - if (!hisi_pcie_pmu_valid_requester_id(pcie_pmu, requester_id))
> - return false;
> - }
> + /* Need to explicitly set filter of "port" or "bdf" */
> + if (!hisi_pcie_get_port(event) &&
> + !hisi_pcie_pmu_valid_requester_id(pcie_pmu, requester_id))
> + return false;
>
> return true;
> }
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-26 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:33 [PATCH v2 0/8] drivers/perf: hisi_pcie: Several updates for HiSilicon PCIe PMU driver Yicong Yang
2024-02-23 10:33 ` [PATCH v2 1/8] drivers/perf: hisi_pcie: Rename hisi_pcie_pmu_{config,clear}_filter() Yicong Yang
2024-02-26 15:11 ` Jonathan Cameron
2024-02-23 10:33 ` [PATCH v2 2/8] drivers/perf: hisi_pcie: Introduce hisi_pcie_pmu_get_event_ctrl_val() Yicong Yang
2024-02-23 10:33 ` [PATCH v2 3/8] drivers/perf: hisi_pcie: Fix incorrect counting under metric mode Yicong Yang
2024-02-26 15:12 ` Jonathan Cameron
2024-02-23 10:33 ` [PATCH v2 4/8] drivers/perf: hisi_pcie: Add more events for counting TLP bandwidth Yicong Yang
2024-02-23 10:33 ` [PATCH v2 5/8] drivers/perf: hisi_pcie: Check the target filter properly Yicong Yang
2024-02-26 15:14 ` Jonathan Cameron [this message]
2024-02-23 10:33 ` [PATCH v2 6/8] drivers/perf: hisi_pcie: Relax the check on related events Yicong Yang
2024-02-26 15:16 ` Jonathan Cameron
2024-02-23 10:33 ` [PATCH v2 7/8] drivers/perf: hisi_pcie: Merge find_related_event() and get_event_idx() Yicong Yang
2024-02-26 15:18 ` Jonathan Cameron
2024-02-23 10:33 ` [PATCH v2 8/8] docs: perf: Update usage for target filter of hisi-pcie-pmu Yicong Yang
2024-02-26 15:20 ` Jonathan Cameron
2024-03-04 15:17 ` [PATCH v2 0/8] drivers/perf: hisi_pcie: Several updates for HiSilicon PCIe PMU driver 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=20240226151442.000053ad@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=fanghao11@huawei.com \
--cc=hejunhao3@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@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;
as well as URLs for NNTP newsgroup(s).