From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Winiarski, Michal" <michal.winiarski@intel.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Alex Williamson" <alex@shazbot.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Yishai Hadas" <yishaih@nvidia.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Brost, Matthew" <matthew.brost@intel.com>,
"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Laguna, Lukasz" <lukasz.laguna@intel.com>,
"Christoph Hellwig" <hch@infradead.org>
Subject: Re: [PATCH v5 28/28] vfio/xe: Add device specific vfio_pci driver variant for Intel graphics
Date: Mon, 17 Nov 2025 13:41:17 -0400 [thread overview]
Message-ID: <20251117174117.GD17968@ziepe.ca> (raw)
In-Reply-To: <ndd4kt4elbm7ixzyouhorgatjwv73ldyjo6bmrbipxvaqzccjs@ssavf6b5ric3>
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
next prev parent reply other threads:[~2025-11-17 17:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 1:04 [PATCH v5 00/28] vfio/xe: Add driver variant for Xe VF migration Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 01/28] drm/xe/pf: Remove GuC version check for migration support Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 02/28] drm/xe: Move migration support to device-level struct Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 03/28] drm/xe/pf: Convert control state to bitmap Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 04/28] drm/xe/pf: Add save/restore control state stubs and connect to debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 05/28] drm/xe/pf: Add data structures and handlers for migration rings Michał Winiarski
2025-11-11 18:35 ` Michal Wajdeczko
2025-11-12 12:12 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 06/28] drm/xe/pf: Add helpers for migration data packet allocation / free Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 07/28] drm/xe/pf: Add support for encap/decap of bitstream to/from packet Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 08/28] drm/xe/pf: Add minimalistic migration descriptor Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 09/28] drm/xe/pf: Expose VF migration data size over debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 10/28] drm/xe: Add sa/guc_buf_cache sync interface Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 11/28] drm/xe: Allow the caller to pass guc_buf_cache size Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 12/28] drm/xe/pf: Increase PF GuC Buffer Cache size and use it for VF migration Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 13/28] drm/xe/pf: Remove GuC migration data save/restore from GT debugfs Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 14/28] drm/xe/pf: Don't save GuC VF migration data on pause Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 15/28] drm/xe/pf: Switch VF migration GuC save/restore to struct migration data Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 16/28] drm/xe/pf: Handle GuC migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 17/28] drm/xe/pf: Add helpers for VF GGTT migration data handling Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 18/28] drm/xe/pf: Handle GGTT migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 19/28] drm/xe/pf: Handle MMIO " Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 20/28] drm/xe/pf: Add helper to retrieve VF's LMEM object Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 21/28] drm/xe/migrate: Add function to copy of VRAM data in chunks Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 22/28] drm/xe/pf: Handle VRAM migration data as part of PF control Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 23/28] drm/xe/pf: Add wait helper for VF FLR Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 24/28] drm/xe/pf: Enable SR-IOV VF migration Michał Winiarski
2025-11-17 18:48 ` Alex Williamson
2025-11-20 9:48 ` Michał Winiarski
2025-11-22 18:10 ` Michal Wajdeczko
2025-11-24 21:19 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 25/28] drm/xe/pci: Introduce a helper to allow VF access to PF xe_device Michał Winiarski
2025-11-22 18:38 ` Michal Wajdeczko
2025-11-24 21:17 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 26/28] drm/xe/pf: Export helpers for VFIO Michał Winiarski
2025-11-22 17:45 ` Michal Wajdeczko
2025-11-24 21:25 ` Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 27/28] drm/intel/bmg: Allow device ID usage with single-argument macros Michał Winiarski
2025-11-11 1:04 ` [PATCH v5 28/28] vfio/xe: Add device specific vfio_pci driver variant for Intel graphics Michał Winiarski
2025-11-11 1:38 ` Tian, Kevin
2025-11-11 8:25 ` Winiarski, Michal
2025-11-11 9:53 ` Tian, Kevin
2025-11-12 13:46 ` Winiarski, Michal
2025-11-17 17:41 ` Jason Gunthorpe [this message]
2025-11-20 12:40 ` Winiarski, Michal
2025-11-21 7:19 ` Tian, Kevin
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=20251117174117.GD17968@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Michal.Wajdeczko@intel.com \
--cc=airlied@gmail.com \
--cc=alex@shazbot.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@infradead.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.winiarski@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=skolothumtho@nvidia.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--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