From: Lukas Wunner <lukas@wunner.de>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Gregory Price <gregory.price@memverge.com>,
"Li, Ming4" <ming4.li@intel.com>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI/DOE: Remove asynchronous task support
Date: Tue, 22 Nov 2022 20:48:29 +0100 [thread overview]
Message-ID: <20221122194829.GB20515@wunner.de> (raw)
In-Reply-To: <20221121174148.0000647d@Huawei.com>
On Mon, Nov 21, 2022 at 05:41:48PM +0000, Jonathan Cameron wrote:
> On Mon, 21 Nov 2022 14:17:37 +0000 "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com> wrote:
> > It's good that this potential issue has been noticed. I think moving
> > the 'find' logic and the xarray from CXL to the PCI core should save
> > a lot of such duplicated works for other drivers using DOE.
> >
> > One more though:
> > For a driver, I think it's only interested in getting a DOE mailbox
> > from a PCI device with specified VID+protocol and using it.
> > The driver doesn't care how is the DOE mailbox instance created and
> > the driver also doesn't want to maintain it.
Totally agree on all of your above points Qiuxu.
> > After using the DOE mailbox instance then the driver puts it back.
That won't be necessary I think. The PCI core allocates all existing
DOE mailboxes and enumerates the supported protocols. Drivers just
ask the PCI core for a mailbox supporting a specific protocol and
are free to use that as long as the PCI device exists.
> There is also a dance around interrupts (once those are supported
> for DOEs in general). Until the PCI driver has requested interrupts
> we can't use them for DOE, but we may want to poll it before that
> stage then switch over.
Thomas Gleixner has returned to his patch sets for dynamic MSI-X
allocation. We'll be able to leverage that to request an interrupt
in the PCI core for DOE before a driver is bound. And a driver
can then get additional MSI-X vectors if needed. Will only work
for MSI-X though, not MSI.
Thanks,
Lukas
next prev parent reply other threads:[~2022-11-22 19:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 22:25 [PATCH] PCI/DOE: Remove asynchronous task support ira.weiny
[not found] ` <20221120022735.4671-1-hdanton@sina.com>
2022-11-20 13:57 ` Ira Weiny
2022-11-21 17:52 ` Jonathan Cameron
2022-11-21 1:39 ` Li, Ming
2022-11-21 2:07 ` Li, Ming
2022-11-21 22:59 ` Ira Weiny
2022-11-22 9:46 ` Jonathan Cameron
2022-11-22 15:55 ` Ira Weiny
2022-11-21 2:01 ` Zhuo, Qiuxu
2022-11-21 11:07 ` Jonathan Cameron
2022-11-21 14:17 ` Zhuo, Qiuxu
2022-11-21 17:41 ` Jonathan Cameron
2022-11-22 19:48 ` Lukas Wunner [this message]
2022-11-21 11:19 ` Jonathan Cameron
2022-11-22 19:28 ` Lukas Wunner
2022-11-22 20:12 ` Dan Williams
2022-11-21 15:24 ` Dan Williams
2022-11-21 17:19 ` Davidlohr Bueso
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=20221122194829.GB20515@wunner.de \
--to=lukas@wunner.de \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=gregory.price@memverge.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ming4.li@intel.com \
--cc=qiuxu.zhuo@intel.com \
--cc=vishal.l.verma@intel.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