On Tue, Nov 04, 2025 at 01:59:45PM +0100, Michał Winiarski wrote:
On Mon, Nov 03, 2025 at 03:30:49PM -0600, Lucas De Marchi wrote:
On Thu, Oct 30, 2025 at 09:31:34PM +0100, Michał Winiarski wrote:
> In order to allow VFIO users to choose the right driver override, VFIO
> driver variant used for VF migration needs to use Intel Graphics PCI
> IDs.
> Add INTEL_VGA_VFIO_DEVICE match that sets VFIO override_only.
>
> Signed-off-by: Michał Winiarski <[email protected]>
> ---
> include/drm/intel/pciids.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/drm/intel/pciids.h b/include/drm/intel/pciids.h
> index b258e79b437ac..d14ce43139a28 100644
> --- a/include/drm/intel/pciids.h
> +++ b/include/drm/intel/pciids.h
> @@ -43,6 +43,13 @@
> .class = PCI_BASE_CLASS_DISPLAY << 16, .class_mask = 0xff << 16, \
> .driver_data = (kernel_ulong_t)(_info), \
> }
> +
> +#define INTEL_VGA_VFIO_DEVICE(_id, _info) { \
> + PCI_DEVICE(PCI_VENDOR_ID_INTEL, (_id)), \
> + .class = PCI_BASE_CLASS_DISPLAY << 16, .class_mask = 0xff << 16, \
> + .driver_data = (kernel_ulong_t)(_info), \
> + .override_only = PCI_ID_F_VFIO_DRIVER_OVERRIDE, \
why do we need this and can't use PCI_DRIVER_OVERRIDE_DEVICE_VFIO()
directly? Note that there are GPUs that wouldn't match the display class
above.
edb660ad79ff ("drm/intel/pciids: Add match on vendor/id only")
5e0de2dfbc1b ("drm/xe/cri: Add CRI platform definition")
Lucas De Marchi
I'll define it on xe-vfio-pci side and use
but no matter where it's defined, why do you need it to match on the
class? The vid/devid should be sufficient.
Lucas De Marchi
