From: Alex Williamson <alex@shazbot.org>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: kvm@vger.kernel.org,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Yishai Hadas" <yishaih@nvidia.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
"Kevin Tian" <kevin.tian@intel.com>,
intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org,
alex@shazbot.org
Subject: Re: [PATCH] vfio/xe: Add CRI and NVL device IDs
Date: Thu, 15 Oct 2026 14:26:16 -0600 [thread overview]
Message-ID: <20261015142616.2811a3a7@shazbot.org> (raw)
In-Reply-To: <20261014131849.157593-2-satyanarayana.k.v.p@intel.com>
On Wed, 14 Oct 2026 18:48:50 +0530
Satyanarayana K V P <satyanarayana.k.v.p@intel.com> wrote:
> Crescent Island (CRI), Nova Lake-S (NVL-S) and Nova Lake-P (NVL-P)
> support SR-IOV in the Xe driver. Add their PCI IDs to the xe-vfio-pci
> device table, so that the generated vfio_pci module aliases allow
> userspace to select this variant driver for their VFs.
>
> Also reordered the table entries.
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Yishai Hadas <yishaih@nvidia.com>
> Cc: Shameer Kolothum <skolothumtho@nvidia.com>
> Cc: Kevin Tian <kevin.tian@intel.com>
> Cc: Alex Williamson <alex@shazbot.org>
> Cc: kvm@vger.kernel.org
> Cc: intel-xe@lists.freedesktop.org
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/vfio/pci/xe/main.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/pci/xe/main.c b/drivers/vfio/pci/xe/main.c
> index cbff5af385ef..8f1237751d51 100644
> --- a/drivers/vfio/pci/xe/main.c
> +++ b/drivers/vfio/pci/xe/main.c
> @@ -574,9 +574,12 @@ static void xe_vfio_pci_remove(struct pci_dev *pdev)
> }
>
> static const struct pci_device_id xe_vfio_pci_table[] = {
> + INTEL_BMG_IDS(INTEL_PCI_VFIO_DEVICE),
> + INTEL_CRI_IDS(INTEL_PCI_VFIO_DEVICE),
> + INTEL_NVLS_IDS(INTEL_PCI_VFIO_DEVICE),
> + INTEL_NVLP_IDS(INTEL_PCI_VFIO_DEVICE),
> INTEL_PTL_IDS(INTEL_PCI_VFIO_DEVICE),
> INTEL_WCL_IDS(INTEL_PCI_VFIO_DEVICE),
> - INTEL_BMG_IDS(INTEL_PCI_VFIO_DEVICE),
> {}
> };
> MODULE_DEVICE_TABLE(pci, xe_vfio_pci_table);
LGTM. Michał? Thanks,
Alex
next prev parent reply other threads:[~2026-10-15 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 13:18 Satyanarayana K V P
2026-10-15 20:26 ` Alex Williamson [this message]
2026-10-15 22:08 ` Michał Winiarski
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=20261015142616.2811a3a7@shazbot.org \
--to=alex@shazbot.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.winiarski@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=skolothumtho@nvidia.com \
--cc=yishaih@nvidia.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
all inboxes | Powered by JetHome®