From: Dave Jiang <dave.jiang@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-cxl@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
linux-perf-users@vger.kernel.org, Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linuxarm@huawei.com
Subject: Re: [RFC PATCH v2 2/4] cxl/pci: Find and register CXL PMU devices
Date: Fri, 21 Oct 2022 10:26:36 -0700 [thread overview]
Message-ID: <d48acad7-9805-2f5e-842e-5af9afae00fa@intel.com> (raw)
In-Reply-To: <20221018121900.00004ff8@huawei.com>
On 10/18/2022 4:19 AM, Jonathan Cameron wrote:
> On Thu, 1 Sep 2022 15:36:23 -0700
> Dave Jiang <dave.jiang@intel.com> wrote:
>
>> On 8/24/2022 3:36 AM, Jonathan Cameron wrote:
>>> CXL PMU devices can be found from entries in the Register
>>> Locator DVSEC.
>>>
>>> In order to register the minimum number of IRQ vectors necessary
>>> to support all CPMUs found, separate the registration into two
>>> steps. First find the devices, and query the IRQs used and then
>>> register the devices. Between these two steps, request the
>>> IRQ vectors necessary and enable bus master support.
>>>
>>> Future IRQ users for CXL type 3 devices (e.g. DOEs) will need to
>>> follow a similar pattern the number of vectors necessary is known
>>> before any parts of the driver stack rely on their availability.
>>>
>>> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>>>
>
>>> +static int cxl_alloc_irq_vectors(struct cxl_dev_state *cxlds, int vectors)
>>> +{
>>> + struct device *dev = cxlds->dev;
>>> + struct pci_dev *pdev = to_pci_dev(dev);
>>> + int rc;
>>> +
>>> + rc = pci_alloc_irq_vectors(pdev, vectors, vectors,
>>> + PCI_IRQ_MSI | PCI_IRQ_MSIX);
>>> + if (rc < 0)
>>> + return rc;
>>> + if (rc != vectors) {
>> I don't think you'll hit here since you passed in vectors for min and
>> max. You'll get -ENOSPC and return from the earlier check.
>>
>> https://elixir.bootlin.com/linux/v6.0-rc3/source/drivers/pci/msi/msi.c#L1005
>>
>> DJ
>>
> Good point. This also applies to the version of the same function in
> Davidlohr's patch set, so I've cut and paste your comment to there.
Somehow I totally missed that reviewing his set. Ooops. Thanks!
>
> Jonathan
next prev parent reply other threads:[~2022-10-21 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 10:36 [RFC PATCH v2 0/4] CXL 3.0 Performance Monitoring Unit support Jonathan Cameron
2022-08-24 10:36 ` [RFC PATCH v2 1/4] cxl: Add function to count regblocks of a given type Jonathan Cameron
2022-09-22 20:19 ` Dave Jiang
2022-08-24 10:36 ` [RFC PATCH v2 2/4] cxl/pci: Find and register CXL PMU devices Jonathan Cameron
2022-09-01 22:36 ` Dave Jiang
2022-10-18 11:19 ` Jonathan Cameron
2022-10-21 17:26 ` Dave Jiang [this message]
2022-08-24 10:36 ` [RFC PATCH v2 3/4] cxl: CXL Performance Monitoring Unit driver Jonathan Cameron
2022-09-22 20:19 ` Dave Jiang
2022-10-18 11:26 ` Jonathan Cameron
2022-08-24 10:36 ` [RFC PATCH v2 4/4] docs: perf: Minimal introduction the the CXL PMU device and driver Jonathan Cameron
2022-09-22 20:41 ` Dave Jiang
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=d48acad7-9805-2f5e-842e-5af9afae00fa@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=vishal.l.verma@intel.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;
as well as URLs for NNTP newsgroup(s).