From: Alex Williamson <alex.williamson@redhat.com>
To: Suman Kumar Chakraborty <suman.kumar.chakraborty@intel.com>
Cc: jgg@ziepe.ca, yishaih@nvidia.com,
shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
linux-crypto@vger.kernel.org, qat-linux@intel.com,
kvm@vger.kernel.org, herbert@gondor.apana.org.au,
giovanni.cabiddu@intel.com
Subject: Re: [PATCH] vfio/qat: add support for intel QAT 6xxx virtual functions
Date: Wed, 16 Jul 2025 14:23:37 -0600 [thread overview]
Message-ID: <20250716142337.64ba908d.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250715081150.1244466-1-suman.kumar.chakraborty@intel.com>
On Tue, 15 Jul 2025 09:11:50 +0100
Suman Kumar Chakraborty <suman.kumar.chakraborty@intel.com> wrote:
> From: Małgorzata Mielnik <malgorzata.mielnik@intel.com>
>
> Extend the qat_vfio_pci variant driver to support QAT 6xxx Virtual
> Functions (VFs). Add the relevant QAT 6xxx VF device IDs to the driver's
> probe table, enabling proper detection and initialization of these devices.
>
> Update the module description to reflect that the driver now supports all
> QAT generations.
>
> Signed-off-by: Małgorzata Mielnik <malgorzata.mielnik@intel.com>
> Signed-off-by: Suman Kumar Chakraborty <suman.kumar.chakraborty@intel.com>
> Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> ---
> drivers/vfio/pci/qat/main.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/pci/qat/main.c b/drivers/vfio/pci/qat/main.c
> index 845ed15b6771..499c9e1d67ee 100644
> --- a/drivers/vfio/pci/qat/main.c
> +++ b/drivers/vfio/pci/qat/main.c
> @@ -675,6 +675,8 @@ static const struct pci_device_id qat_vf_vfio_pci_table[] = {
> { PCI_DRIVER_OVERRIDE_DEVICE_VFIO(PCI_VENDOR_ID_INTEL, 0x4941) },
> { PCI_DRIVER_OVERRIDE_DEVICE_VFIO(PCI_VENDOR_ID_INTEL, 0x4943) },
> { PCI_DRIVER_OVERRIDE_DEVICE_VFIO(PCI_VENDOR_ID_INTEL, 0x4945) },
> + /* Intel QAT GEN6 6xxx VF device */
> + { PCI_DRIVER_OVERRIDE_DEVICE_VFIO(PCI_VENDOR_ID_INTEL, 0x4949) },
> {}
> };
> MODULE_DEVICE_TABLE(pci, qat_vf_vfio_pci_table);
> @@ -696,5 +698,5 @@ module_pci_driver(qat_vf_vfio_pci_driver);
>
> MODULE_LICENSE("GPL");
> MODULE_AUTHOR("Xin Zeng <xin.zeng@intel.com>");
> -MODULE_DESCRIPTION("QAT VFIO PCI - VFIO PCI driver with live migration support for Intel(R) QAT GEN4 device family");
> +MODULE_DESCRIPTION("QAT VFIO PCI - VFIO PCI driver with live migration support for Intel(R) QAT device family");
> MODULE_IMPORT_NS("CRYPTO_QAT");
>
> base-commit: bfeda8f971d01d0c1d0e3f4cf9d4e2b0a2b09d89
Applied to vfio next branch for v6.17. Thanks,
Alex
prev parent reply other threads:[~2025-07-16 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 8:11 [PATCH] vfio/qat: add support for intel QAT 6xxx virtual functions Suman Kumar Chakraborty
2025-07-16 20:23 ` Alex Williamson [this message]
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=20250716142337.64ba908d.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=suman.kumar.chakraborty@intel.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;
as well as URLs for NNTP newsgroup(s).