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

Message-ID: <aSZVybx3cgPw6HQh@lstrano-desk.jf.intel.com>
Date: Tue, 25 Nov 2025 17:20:09 -0800
From: Matthew Brost <matthew.brost@...el.com>
To: Alex Williamson <alex@...zbot.org>
CC: Michał Winiarski <michal.winiarski@...el.com>, "Lucas De
 Marchi" <lucas.demarchi@...el.com>, Thomas Hellström
	<thomas.hellstrom@...ux.intel.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, 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

> 
> Alex