From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Ira Weiny <ira.weiny@intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
"Dan Williams" <dan.j.williams@intel.com>, <dave.jiang@intel.com>,
<alison.schofield@intel.com>, <bwidawsk@kernel.org>,
<vishal.l.verma@intel.com>, <a.manzanares@samsung.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/2] cxl/pci: Add generic MSI-X/MSI irq support
Date: Thu, 3 Nov 2022 18:09:16 +0000 [thread overview]
Message-ID: <20221103180916.00000bae@Huawei.com> (raw)
In-Reply-To: <20221103001833.n2gsoflnji3pcsfr@offworld>
On Wed, 2 Nov 2022 17:18:33 -0700
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Wed, 02 Nov 2022, Ira Weiny wrote:
>
> >On Wed, Nov 02, 2022 at 10:15:24AM -0700, Davidlohr Bueso wrote:
> >> Most CXL features that can have irqs will normally use only the first 16,
> >> with the exception of isolation (cxl 3.0), which per the spec is up to 32.
> >
> >Dan, Dave, and I were discussing this and we agree. For now the only things
> >people are working on are within the first 16 so why not just request 16 as the
> >max for now?
>
> It is a fair compromise, yes.
works for me.
next prev parent reply other threads:[~2022-11-03 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221018030010.20913-1-dave@stgolabs.net>
[not found] ` <20221018030010.20913-2-dave@stgolabs.net>
[not found] ` <63546939ea062_1419294f6@dwillia2-mobl3.amr.corp.intel.com.notmuch>
[not found] ` <Y1XX1tVLQoYmYnSM@iweiny-mobl>
[not found] ` <6355f3b933235_1d21294da@dwillia2-mobl3.amr.corp.intel.com.notmuch>
2022-10-24 12:36 ` [PATCH 1/2] cxl/pci: Add generic MSI-X/MSI irq support Jonathan Cameron
2022-10-25 23:25 ` Bjorn Helgaas
2022-10-30 8:38 ` Christoph Hellwig
2022-11-02 17:15 ` Davidlohr Bueso
2022-11-02 22:54 ` Bjorn Helgaas
2022-11-02 23:42 ` Ira Weiny
2022-11-03 0:18 ` Davidlohr Bueso
2022-11-03 18:09 ` Jonathan Cameron [this message]
2022-11-10 3:30 ` Ira Weiny
2022-11-11 21:18 ` Davidlohr Bueso
2022-11-03 18:08 ` Jonathan Cameron
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=20221103180916.00000bae@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=bhelgaas@google.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).