Linux CXL
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: dan.j.williams@intel.com
Cc: ira.weiny@intel.com, Jonathan.Cameron@huawei.com,
	dave.jiang@intel.com, alison.schofield@intel.com,
	vishal.l.verma@intel.com, bwidawsk@kernel.org,
	a.manzanares@samsung.com, linux-kernel@vger.kernel.org,
	linux-cxl@vger.kernel.org, dave@stgolabs.net
Subject: [PATCH v2 0/2] cxl: Add basic MSI/MSI-X support
Date: Fri, 14 Oct 2022 12:49:28 -0700	[thread overview]
Message-ID: <20221014194930.2630416-1-dave@stgolabs.net> (raw)

Hi,

Changes from v1 (https://lore.kernel.org/all/20221012180432.473373-1-dave@stgolabs.net/):

- Do not populate the cxl_irq_cap_table. (Jonathan)
- Moved vector allocation further above. (Jonathan)
- Added an irq_type flag, makes sense to have for checking during setup.
- Left no irq support as an error, but mentioned that in the the call is
  in the context of allocation. Otherwise this makes the user handling
  unnecessarily difficult.
- Picked up Dave's review.
- Added a second patch which adds the basic mailbox support (Dave)


Patch 1 contains updates for the generic table handling.

Patch 2 populates the table and adds mailbox support.

Please consider for v6.3.

Thanks!

Davidlohr Bueso (2):
  cxl/pci: Add generic MSI/MSI-X interrupt support
  cxl/mbox: Wire up basic irq support

 drivers/cxl/cxl.h    |  6 +++
 drivers/cxl/cxlmem.h |  2 +
 drivers/cxl/pci.c    | 91 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 99 insertions(+)

--
2.37.3


             reply	other threads:[~2022-10-14 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 19:49 Davidlohr Bueso [this message]
2022-10-14 19:49 ` [PATCH 1/2] cxl/pci: Add generic MSI/MSI-X interrupt support Davidlohr Bueso
2022-10-16 22:10   ` Ira Weiny
2022-10-17  0:37     ` Davidlohr Bueso
2022-10-17 10:06       ` Jonathan Cameron
2022-10-14 19:49 ` [PATCH 2/2] cxl/mbox: Wire up basic irq support Davidlohr Bueso
2022-10-16 22:06   ` Ira Weiny
2022-10-17 10: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=20221014194930.2630416-1-dave@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@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