From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: kaishen@linux.alibaba.com, helgaas@kernel.org,
yangyicong@huawei.com, will@kernel.org,
Jonathan.Cameron@huawei.com, baolin.wang@linux.alibaba.com,
robin.murphy@arm.com, chengyou@linux.alibaba.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
rdunlap@infradead.org, mark.rutland@arm.com,
zhuo.song@linux.alibaba.com, renyu.zj@linux.alibaba.com
Subject: Re: [PATCH v10 4/5] drivers/perf: add DesignWare PCIe PMU driver
Date: Thu, 16 Nov 2023 16:02:38 +0800 [thread overview]
Message-ID: <7e383d7f-8df5-4d49-a45e-3dbe23b2c925@linux.alibaba.com> (raw)
In-Reply-To: <32626689-c8b1-9bd-b00-5285c633bfbc@os.amperecomputing.com>
On 2023/11/16 11:50, Ilkka Koskinen wrote:
>
> Hi Shuai,
>
> I have a few comments below
>
>
...
>
>> +static void dwc_pcie_pmu_time_based_event_enable(struct dwc_pcie_pmu *pcie_pmu,
>> + bool enable)
>> +{
>> + struct pci_dev *pdev = pcie_pmu->pdev;
>> + u16 ras_des_offset = pcie_pmu->ras_des_offset;
>> +
>> + if (enable)
>> + pci_clear_and_set_dword(pdev,
>> + ras_des_offset + DWC_PCIE_TIME_BASED_ANAL_CTL,
>> + DWC_PCIE_TIME_BASED_TIMER_START, 0x1);
>> + else
>> + pci_clear_and_set_dword(pdev,
>> + ras_des_offset + DWC_PCIE_TIME_BASED_ANAL_CTL,
>> + DWC_PCIE_TIME_BASED_TIMER_START, 0x0);
>
> It's a matter of taste, but you could simply do:
>
> pci_clear_and_set_dword(pdev,
> ras_des_offset + DWC_PCIE_TIME_BASED_ANAL_CTL,
> DWC_PCIE_TIME_BASED_TIMER_START, enable);
>
>
> However, I'm fine with either way.
Good suggestion, will fix it.
>
>> +static u64 dwc_pcie_pmu_read_lane_event_counter(struct perf_event *event)
>> +{
>> + struct dwc_pcie_pmu *pcie_pmu = to_dwc_pcie_pmu(event->pmu);
>> + struct pci_dev *pdev = pcie_pmu->pdev;
>> + u16 ras_des_offset = pcie_pmu->ras_des_offset;
>> + u32 val;
>> +
>> + pci_read_config_dword(pdev, ras_des_offset + DWC_PCIE_EVENT_CNT_DATA, &val);
>> +
>> + return val;
>> +}
>
> ...
>
>> +static int dwc_pcie_register_dev(struct pci_dev *pdev)
>> +{
>> + struct platform_device *plat_dev;
>> + struct dwc_pcie_dev_info *dev_info;
>> + int ret;
>> + u32 bdf;
>> +
>> + bdf = PCI_DEVID(pdev->bus->number, pdev->devfn);
>> + plat_dev = platform_device_register_data(NULL, "dwc_pcie_pmu", bdf,
>> + pdev, sizeof(*pdev));
>> + ret = PTR_ERR_OR_ZERO(plat_dev);
>> + if (ret)
>> + return ret;
>
> platform_device_register_data() doesn't return a null pointer and you don't really need 'ret'. You could do something like instead:
>
> if (IS_ERR(plat_dev))
> return PTR_ERR(plat_dev);
>
>> + dev_info = kzalloc(sizeof(*dev_info), GFP_KERNEL);
>> + if (!dev_info)
>> + return -ENOMEM;
>> +
>> + /* Cache platform device to handle pci device hotplug */
>> + dev_info->plat_dev = plat_dev;
>> + dev_info->pdev = pdev;
>> + list_add(&dev_info->dev_node, &dwc_pcie_dev_info_head);
>> +
>> + return 0;
>> +}
>> +
>> +static int dwc_pcie_pmu_notifier(struct notifier_block *nb,
>> + unsigned long action, void *data)
>> +{
>> + struct device *dev = data;
>> + struct pci_dev *pdev = to_pci_dev(dev);
>> + struct dwc_pcie_dev_info *dev_info;
>> +
>> + switch (action) {
>> + case BUS_NOTIFY_ADD_DEVICE:
>> + if (!dwc_pcie_match_des_cap(pdev))
>> + return NOTIFY_DONE;
>> + if (dwc_pcie_register_dev(pdev))
>> + return NOTIFY_BAD;
>> + break;
>> + case BUS_NOTIFY_DEL_DEVICE:
>> + dev_info = dwc_pcie_find_dev_info(pdev);
>> + if (!dev_info)
>> + return NOTIFY_DONE;
>> + dwc_pcie_unregister_dev(dev_info);
>> + break;
>> + }
>> +
>> + return NOTIFY_OK;
>> +}
>> +
>> +static struct notifier_block dwc_pcie_pmu_nb = {
>> + .notifier_call = dwc_pcie_pmu_notifier,
>> +};
>> +
>> +static int dwc_pcie_pmu_probe(struct platform_device *plat_dev)
>> +{
>> + struct pci_dev *pdev = plat_dev->dev.platform_data;
>> + struct dwc_pcie_pmu *pcie_pmu;
>> + char *name;
>> + u32 bdf, val;
>> + u16 vsec;
>> + int ret;
>> +
>> + vsec = pci_find_vsec_capability(pdev, PCI_VENDOR_ID_ALIBABA,
>> + DWC_PCIE_VSEC_RAS_DES_ID);
>
> You nicely changed to use vendor list in this version but here the driver still tries to find Alibaba specific capability.
Sorry, I missed here.
> I guess, you could search again using the vendor list. The other option would be to make dwc_pcie_match_des_cap() to return the vendor id, pass it to dwc_pcie_register_dev(), which would add it to device's platform data with
> the pointer to the pci device.
The dwc_pcie_pmu_probe() is called by device which has DWC_PCIE_VSEC_RAS_DES_ID cap.
So I guess I can use pdev->vendor directly here, e.g?
pci_find_vsec_capability(pdev, pdev->vendor, DWC_PCIE_VSEC_RAS_DES_ID);
Best Regards,
Shuai
_______________________________________________
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:[~2023-11-16 8:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 13:32 [PATCH v10 0/5] drivers/perf: add Synopsys DesignWare PCIe PMU driver support Shuai Xue
2023-11-04 13:32 ` [PATCH v10 1/5] docs: perf: Add description for Synopsys DesignWare PCIe PMU driver Shuai Xue
2023-11-04 13:32 ` [PATCH v10 2/5] PCI: Add Alibaba Vendor ID to linux/pci_ids.h Shuai Xue
2023-11-04 13:32 ` [PATCH v10 3/5] PCI: move pci_clear_and_set_dword helper to pci header Shuai Xue
2023-11-07 15:03 ` Bjorn Helgaas
2023-11-08 0:51 ` Shuai Xue
2023-11-04 13:32 ` [PATCH v10 4/5] drivers/perf: add DesignWare PCIe PMU driver Shuai Xue
2023-11-15 0:07 ` Ilkka Koskinen
2023-11-15 1:26 ` Shuai Xue
2023-11-16 0:48 ` Ilkka Koskinen
2023-11-16 3:50 ` Ilkka Koskinen
2023-11-16 8:02 ` Shuai Xue [this message]
2023-11-16 19:02 ` Ilkka Koskinen
2023-11-04 13:32 ` [PATCH v10 5/5] MAINTAINERS: add maintainers for " Shuai Xue
2023-11-16 0:57 ` [PATCH v10 0/5] drivers/perf: add Synopsys DesignWare PCIe PMU driver support Ilkka Koskinen
2023-11-16 1:49 ` Shuai Xue
2023-11-16 2:42 ` Ilkka Koskinen
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=7e383d7f-8df5-4d49-a45e-3dbe23b2c925@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=helgaas@kernel.org \
--cc=ilkka@os.amperecomputing.com \
--cc=kaishen@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rdunlap@infradead.org \
--cc=renyu.zj@linux.alibaba.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@huawei.com \
--cc=zhuo.song@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;
as well as URLs for NNTP newsgroup(s).