From: Alex Williamson <alex@shazbot.org>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: <intel-xe@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Yishai Hadas <yishaih@nvidia.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
Kevin Tian <kevin.tian@intel.com>, <stable@vger.kernel.org>,
alex@shazbot.org
Subject: Re: [PATCH v2 1/2] vfio/xe: Reorganize the init to decouple migration from reset
Date: Mon, 13 Apr 2026 15:58:27 -0600 [thread overview]
Message-ID: <20260413155827.494b7f0e@shazbot.org> (raw)
In-Reply-To: <20260410224948.900550-1-michal.winiarski@intel.com>
On Sat, 11 Apr 2026 00:49:47 +0200
Michał Winiarski <michal.winiarski@intel.com> wrote:
> Attempting to issue reset on VF devices that don't support migration
> leads to the following:
[...]
> This is caused by the fact that some of the xe_vfio_pci_core_device
> members needed for handling reset are only initialized as part of
> migration init.
>
> Fix the problem by reorganizing the code to decouple VF init from
> migration init.
>
> Fixes: 1f5556ec8b9ef ("vfio/xe: Add device specific vfio_pci driver variant for Intel graphics")
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/7352
> Cc: stable@vger.kernel.org
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> ---
> drivers/vfio/pci/xe/main.c | 43 ++++++++++++++++++++++----------------
> 1 file changed, 25 insertions(+), 18 deletions(-)
Applied to vfio next branch for v7.1. Thanks,
Alex
prev parent reply other threads:[~2026-04-13 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 22:49 [PATCH v2 1/2] vfio/xe: Reorganize the init to decouple migration from reset Michał Winiarski
2026-04-10 22:49 ` [PATCH v2 2/2] vfio/xe: Add a missing vfio_pci_core_release_dev() Michał Winiarski
2026-04-13 6:42 ` [PATCH v2 1/2] vfio/xe: Reorganize the init to decouple migration from reset Tian, Kevin
2026-04-13 21:58 ` Alex Williamson [this message]
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=20260413155827.494b7f0e@shazbot.org \
--to=alex@shazbot.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.winiarski@intel.com \
--cc=skolothumtho@nvidia.com \
--cc=stable@vger.kernel.org \
--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