linux-kernel - Re: [PATCH v6 0/4] vfio/xe: Add driver variant for Xe VF migration

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c5f1344daeec43e5b5d9e6536c8c8b8a13323f7a.camel@linux.intel.com>
Date: Wed, 26 Nov 2025 12:38:34 +0100
From: Thomas Hellström <thomas.hellstrom@...ux.intel.com>
To: Matthew Brost <matthew.brost@...el.com>, Alex Williamson
 <alex@...zbot.org>
Cc: Michał Winiarski <michal.winiarski@...el.com>, Lucas De
 Marchi <lucas.demarchi@...el.com>, Rodrigo Vivi <rodrigo.vivi@...el.com>,
 Jason Gunthorpe	 <jgg@...pe.ca>, Yishai Hadas <yishaih@...dia.com>, Kevin
 Tian	 <kevin.tian@...el.com>, Shameer Kolothum <skolothumtho@...dia.com>, 
	intel-xe@...ts.freedesktop.org, linux-kernel@...r.kernel.org, 
	kvm@...r.kernel.org, Michal Wajdeczko <michal.wajdeczko@...el.com>, 
	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>, Lukasz Laguna	 <lukasz.laguna@...el.com>, Christoph
 Hellwig <hch@...radead.org>
Subject: Re: [PATCH v6 0/4] vfio/xe: Add driver variant for Xe VF migration

On Tue, 2025-11-25 at 17:20 -0800, Matthew Brost wrote:
> On Tue, Nov 25, 2025 at 01:13:15PM -0700, Alex Williamson wrote:
> > On Tue, 25 Nov 2025 00:08:37 +0100
> > Michał Winiarski <michal.winiarski@...el.com> wrote:
> > 
> > > Hi,
> > > 
> > > We're now at v6, thanks for all the review feedback.
> > > 
> > > First 24 patches are now already merged through drm-tip tree, and
> > > I hope
> > > we can get the remaining ones through the VFIO tree.
> > 
> > Are all those dependencies in a topic branch somewhere?  Otherwise
> > to
> > go in through vfio would mean we need to rebase our next branch
> > after
> > drm is merged.  LPC is happening during this merge window, so we
> > may
> > not be able to achieve that leniency in ordering.  Is the better
> > approach to get acks on the variant driver and funnel the whole
> > thing
> > through the drm tree?  Thanks,
> 
> +1 on merging through drm if VFIO maintainers are ok with this. I've
> done this for various drm external changes in the past with
> maintainers
> acks.
> 
> Matt

@Michal Winiarski

Are these patches depending on any other VFIO changes that are queued
for 6.19? 

If not and with proper VFIO acks, I could ask Dave / Sima to allow this
for drm-xe-next-fixes pull. Then I also would need a strong
justification for it being in 6.19 rather in 7.0.

Otherwise we'd need to have the VFIO changes it depends on in a topic
branch, or target this for 7.0 and hold off the merge until we can
backmerge 6.9-rc1.

Thanks,
Thomas


> 
> > 
> > Alex