From: Yicong Yang <yangyicong@huawei.com>
To: <suzuki.poulose@arm.com>
Cc: <mathieu.poirier@linaro.org>, <jonathan.cameron@huawei.com>,
<yangyicong@hisilicon.com>, <alexander.shishkin@linux.intel.com>,
<helgaas@kernel.org>, <linux-pci@vger.kernel.org>,
<prime.zeng@huawei.com>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] hwtracing: hisi_ptt: Only add the supported devices to the filters list
Date: Thu, 19 Jan 2023 17:10:30 +0800 [thread overview]
Message-ID: <252ff08d-55ed-b733-6b66-4ea40f07e501@huawei.com> (raw)
In-Reply-To: <20230112112201.16283-1-yangyicong@huawei.com>
Hi Suzuki,
Any comments or is it ok to pick these two patches?
Hope to not miss this cycle since there's one fix :)
Thanks,
Yicong
On 2023/1/12 19:22, Yicong Yang wrote:
> From: Yicong Yang <yangyicong@hisilicon.com>
>
> The PTT device can only support the devices on the same PCIe core,
> within BDF range [lower_bdf, upper_bdf]. It's not correct to assume
> the devices on the root bus are from the same PCIe core, there are
> cases that root ports from different PCIe core are sharing the same
> bus. So check when initializing the filters list.
>
> Fixes: ff0de066b463 ("hwtracing: hisi_ptt: Add trace function support for HiSilicon PCIe Tune and Trace device")
> Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> Change since v2:
> - Refine the commit per Bjorn
> Link: https://lore.kernel.org/linux-pci/20230110130833.53474-1-yangyicong@huawei.com/
>
> Change since v1:
> - Add tags from Jonathan
> Link: https://lore.kernel.org/linux-pci/20221122120209.25682-1-yangyicong@huawei.com/raw
>
> drivers/hwtracing/ptt/hisi_ptt.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/hwtracing/ptt/hisi_ptt.c b/drivers/hwtracing/ptt/hisi_ptt.c
> index 5d5526aa60c4..30f1525639b5 100644
> --- a/drivers/hwtracing/ptt/hisi_ptt.c
> +++ b/drivers/hwtracing/ptt/hisi_ptt.c
> @@ -356,8 +356,18 @@ static int hisi_ptt_register_irq(struct hisi_ptt *hisi_ptt)
>
> static int hisi_ptt_init_filters(struct pci_dev *pdev, void *data)
> {
> + struct pci_dev *root_port = pcie_find_root_port(pdev);
> struct hisi_ptt_filter_desc *filter;
> struct hisi_ptt *hisi_ptt = data;
> + u32 port_devid;
> +
> + if (!root_port)
> + return 0;
> +
> + port_devid = PCI_DEVID(root_port->bus->number, root_port->devfn);
> + if (port_devid < hisi_ptt->lower_bdf ||
> + port_devid > hisi_ptt->upper_bdf)
> + return 0;
>
> /*
> * We won't fail the probe if filter allocation failed here. The filters
>
next prev parent reply other threads:[~2023-01-19 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 11:22 [PATCH v3 1/2] hwtracing: hisi_ptt: Only add the supported devices to the filters list Yicong Yang
2023-01-12 11:22 ` [PATCH v3 2/2] MAINTAINERS: Update the entries for HiSilicon PTT device driver Yicong Yang
2023-01-19 9:10 ` Yicong Yang [this message]
2023-01-19 9:55 ` [PATCH v3 1/2] hwtracing: hisi_ptt: Only add the supported devices to the filters list Suzuki K Poulose
2023-01-20 9:20 ` Yicong Yang
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=252ff08d-55ed-b733-6b66-4ea40f07e501@huawei.com \
--to=yangyicong@huawei.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mathieu.poirier@linaro.org \
--cc=prime.zeng@huawei.com \
--cc=suzuki.poulose@arm.com \
--cc=yangyicong@hisilicon.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