From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, mjrosato@linux.ibm.com,
jjherne@linux.ibm.com, pasic@linux.ibm.com, clg@redhat.com,
farman@linux.ibm.com, borntraeger@linux.ibm.com,
alex@shazbot.org, cohuck@redhat.com,
Anthony Krowiak <akrowiak@linux.ibm.com>
Subject: [PATCH v2 0/2] Enable live migration of vfio-ap devices
Date: Thu, 9 Apr 2026 10:13:43 -0400 [thread overview]
Message-ID: <20260409141352.997844-1-akrowiak@linux.ibm.com> (raw)
This patch series enables live guest migration for s390 guests using
AP (Adjunct Processor) crypto devices passed through via the VFIO
framework.
The s390 AP architecture provides cryptographic coprocessor and accelerator
functions to guests. The vfio_ap device driver allows these AP devices to
be passed through to KVM guests, giving them access to the cryptographic
capabilities of CEXxS crypto cards.
Previously, guests using vfio-ap devices could not be migrated because the
device was marked as unmigratable. This series implements the necessary
QEMU-side support to enable migration by:
* Removing the migration blocker and adding proper VMState infrastructure
* Implementing the VFIO migration callbacks that coordinate with the kernel
vfio_ap driver to save and restore device state
The actual AP device state (queue configurations, crypto adapter
assignments, etc.) is managed entirely by the kernel vfio_ap driver and
transferred via the VFIO migration protocol. QEMU's role is to coordinate
the migration process and ensure proper sequencing of state transfers.
This implementation follows the standard VFIO migration framework used by
other VFIO device types (GPUs, network adapters, etc.) and integrates
cleanly with QEMU's existing migration infrastructure.
Dependencies:
------------
* Requires corresponding kernel patches that implement the VFIO migration
protocol in the vfio_ap driver
- see kernel patch series at https://lkml.org/lkml/2026/4/7/1991
* Kernel must support VFIO_DEVICE_FEATURE_MIGRATION for vfio-ap devices
Anthony Krowiak (1):
hw/vfio/ap: Callbacks for migration of guests with pass-through access
to AP devices
Anthony Krowiak (1):
hw/vfio/ap: Extend vfio device state description to facilitate live
migration
hw/vfio/ap.c | 60 ++++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 49 insertions(+), 11 deletions(-)
--
2.52.0
next reply other threads:[~2026-04-09 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 14:13 Anthony Krowiak [this message]
2026-04-09 14:13 ` [PATCH v2 1/2] hw/vfio/ap: Extend vfio device state description to facilitate live migration Anthony Krowiak
2026-04-10 8:17 ` Cédric Le Goater
2026-04-10 10:48 ` Anthony Krowiak
2026-04-09 14:13 ` [PATCH v2 2/2] hw/vfio/ap: Callbacks for migration of guests with pass-through access to AP devices Anthony Krowiak
2026-04-10 8:19 ` Cédric Le Goater
2026-04-10 10:47 ` Anthony Krowiak
2026-04-11 7:20 ` Cédric Le Goater
2026-04-10 10:50 ` Anthony Krowiak
2026-04-11 7:56 ` Cédric Le Goater
2026-04-13 15:23 ` Anthony Krowiak
2026-04-16 15:05 ` Cédric Le Goater
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=20260409141352.997844-1-akrowiak@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.