linux-kernel - RE: [PATCH v5 28/28] vfio/xe: Add device specific vfio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <BN9PR11MB527619CD77F553EE93D514AE8CD5A@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Fri, 21 Nov 2025 07:19:23 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: "Winiarski, Michal" <michal.winiarski@...el.com>, Jason Gunthorpe
	<jgg@...pe.ca>
CC: Alex Williamson <alex@...zbot.org>, "De Marchi, Lucas"
	<lucas.demarchi@...el.com>, Thomas Hellström
	<thomas.hellstrom@...ux.intel.com>, "Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
	Yishai Hadas <yishaih@...dia.com>, Shameer Kolothum
	<skolothumtho@...dia.com>, "intel-xe@...ts.freedesktop.org"
	<intel-xe@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"Brost, Matthew" <matthew.brost@...el.com>, "Wajdeczko, Michal"
	<Michal.Wajdeczko@...el.com>, "dri-devel@...ts.freedesktop.org"
	<dri-devel@...ts.freedesktop.org>, Jani Nikula <jani.nikula@...ux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, Tvrtko Ursulin
	<tursulin@...ulin.net>, David Airlie <airlied@...il.com>, Simona Vetter
	<simona@...ll.ch>, "Laguna, Lukasz" <lukasz.laguna@...el.com>, "Christoph
 Hellwig" <hch@...radead.org>
Subject: RE: [PATCH v5 28/28] vfio/xe: Add device specific vfio_pci driver
 variant for Intel graphics

> From: Winiarski, Michal <michal.winiarski@...el.com>
> Sent: Thursday, November 20, 2025 8:40 PM
> 
> On Mon, Nov 17, 2025 at 01:41:17PM -0400, Jason Gunthorpe wrote:
> > On Wed, Nov 12, 2025 at 02:46:08PM +0100, Winiarski, Michal wrote:
> > > > > I agree that it should be done in the core eventually.
> > > > > I didn't view it as something blocking next revision, as the discussion
> > > > > was in the context of converting every driver, which is something that
> > > > > probably shouldn't be done as part of this series.
> > > >
> > > > well it doesn't make much sense to push a new driver specific
> > > > implementation when the core approach is preferred.
> > >
> > > This would generally mean that accepting any new VFIO driver variant
> > > would be blocked until core approach materializes.
> > >
> > > Jason, can you confirm that this is indeed what you have in mind?
> > > Just to determine how urgent the core-side changes are, and whether
> > > there's anything we can do to help with that.
> >
> > A core approach would be nice, but I also haven't looked at what it
> > would be like.
> >
> > I think if you post a small series trying to build one and convert
> > some of the existing drivers it would be sufficient to let this go
> > ahead.
> >
> > Jason
> 
> I posted a series that attempts to do just that.
> https://lore.kernel.org/lkml/20251120123647.3522082-1-
> michal.winiarski@...el.com/
> 
> I would appreciate if we could move forward with the review of this
> series independently. It should be relatively straightforward to convert
> this driver once we're able to get an alignment on specific core-side
> solution.
> 

that core series is simple. so whichever goes first is ok to me.

for what it stands here:

Reviewed-by: Kevin Tian <kevin.tian@...el.com>