From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Cc: jjherne@linux.ibm.com, borntraeger@de.ibm.com,
mjrosato@linux.ibm.com, pasic@linux.ibm.com, alex@shazbot.org,
kwankhede@nvidia.com, fiuczy@linux.ibm.com, pbonzini@redhat.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com,
agordeev@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com
Subject: [PATCH v12 12/14] s390/vfio-ap: Set up for vfio-ap device migration
Date: Fri, 6 Nov 2026 10:22:57 -0500 [thread overview]
Message-ID: <20261106152259.1360651-13-akrowiak@linux.ibm.com> (raw)
In-Reply-To: <20261106152259.1360651-1-akrowiak@linux.ibm.com>
In order to facilitate vfio-ap device migration:
* The function pointers to the callbacks used to facilitate migration of a
vfio-ap device must be plugged in. These function pointers are specified
via the fields contained in a struct vfio_migration_ops instance:
migration_set_state: Set the migration state of the vfio-ap device
migration_get_state: Get the migration state of the vfio-ap device
migration_get_data_size: Get the estimated data number bytes of
data that will be required to complete
STOP_COPY
* The migration_flags field of the struct vfio_device instance is set to
VFIO_MIGRATION_STOP_COPY to indicate that STOP, STOP_COPY and RESUMING
are the migration states supported for vfio-ap device migration.
* The initial migration state of the vfio-ap device is set to RUNNING
* The boolean flag indicating that all data sent from userspace during the
RESUMINMG phase has been received is initialized to false.
Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
---
drivers/s390/crypto/vfio_ap_migration.c | 24 ++++++++++++++++++++++++
drivers/s390/crypto/vfio_ap_ops.c | 10 ++++++++++
drivers/s390/crypto/vfio_ap_private.h | 1 +
3 files changed, 35 insertions(+)
diff --git a/drivers/s390/crypto/vfio_ap_migration.c b/drivers/s390/crypto/vfio_ap_migration.c
index 4af734aeee17..924c25585987 100644
--- a/drivers/s390/crypto/vfio_ap_migration.c
+++ b/drivers/s390/crypto/vfio_ap_migration.c
@@ -217,6 +217,30 @@ static int vfio_ap_release_mig_file(struct inode *file_inode, struct file *filp)
return 0;
}
+static const struct vfio_migration_ops vfio_ap_migration_ops;
+
+/**
+ * vfio_ap_setup_vfio_device_migration:
+ *
+ * Plug the object containing the function pointers to the migration callbacks
+ * used to facilitate migration into the vfio device and set the flags
+ * indicating migration states STOP, STOP_COPY and RESUMING are supported.
+ *
+ * @matrix_mdev: pointer to object containing the vfio device (vdev)
+ */
+void vfio_ap_setup_vfio_device_migration(struct ap_matrix_mdev *matrix_mdev)
+{
+ /*
+ * Live guest migration is not supported for SE guests, so there is no
+ * need to initialize the migration capabilities.
+ */
+ if (ap_is_se_guest())
+ return;
+
+ matrix_mdev->vdev.migration_flags = VFIO_MIGRATION_STOP_COPY;
+ matrix_mdev->vdev.mig_ops = &vfio_ap_migration_ops;
+}
+
/**
* validate_stop_copy_read_parms: Validate the input parameters to the
* vfio_ap_stop_copy_read function
diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
index 8d70089eb9c9..52de74dc2c6c 100644
--- a/drivers/s390/crypto/vfio_ap_ops.c
+++ b/drivers/s390/crypto/vfio_ap_ops.c
@@ -811,9 +811,19 @@ static int vfio_ap_mdev_probe(struct mdev_device *mdev)
matrix_mdev = vfio_alloc_device(ap_matrix_mdev, vdev, &mdev->dev,
&vfio_ap_matrix_dev_ops);
+
if (IS_ERR(matrix_mdev))
return PTR_ERR(matrix_mdev);
+ /*
+ * Set up vfio-ap device migration before calling
+ * vfio_register_emulated_iommu_dev; otherwise, the VFIO core
+ * will see mig_ops as NULL during the registration. This could
+ * prevent the VFIO core from properly setting up migration
+ * infrastructure like debugfs entries.
+ */
+ vfio_ap_setup_vfio_device_migration(matrix_mdev);
+
ret = vfio_register_emulated_iommu_dev(&matrix_mdev->vdev);
if (ret)
goto err_put_vdev;
diff --git a/drivers/s390/crypto/vfio_ap_private.h b/drivers/s390/crypto/vfio_ap_private.h
index c6e577064e7e..19772e59fdc6 100644
--- a/drivers/s390/crypto/vfio_ap_private.h
+++ b/drivers/s390/crypto/vfio_ap_private.h
@@ -173,6 +173,7 @@ void vfio_ap_on_scan_complete(struct ap_config_info *new_config_info,
struct ap_config_info *old_config_info);
int vfio_ap_init_migration_data(struct ap_matrix_mdev *matrix_mdev);
+void vfio_ap_setup_vfio_device_migration(struct ap_matrix_mdev *matrix_mdev);
void vfio_ap_release_migration_data(struct ap_matrix_mdev *matrix_mdev);
void vfio_ap_reset_migration_state(struct ap_matrix_mdev *matrix_mdev);
--
2.53.0
next prev parent reply other threads:[~2026-11-06 15:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:22 [PATCH v12 00/14] s390/vfio-ap: Add live guest migration support Anthony Krowiak
2026-11-06 15:22 ` [PATCH v12 01/14] s390/vfio-ap: Provide function to get the number of queues assigned to mdev Anthony Krowiak
2026-11-06 15:30 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 02/14] s390/vfio-ap: Data structures for facilitating vfio device migration Anthony Krowiak
2026-11-06 15:30 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 03/14] s390/vfio-ap: Functions to initialize/release vfio device migration data Anthony Krowiak
2026-11-06 15:47 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 04/14] s390/vfio-ap: Reset migration state on VFIO_DEVICE_RESET and device close Anthony Krowiak
2026-11-06 15:32 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 05/14] s390/vfio-ap: Callback to get/set vfio device mig state during guest migration Anthony Krowiak
2026-11-06 15:44 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 06/14] s390/vfio-ap: Transition guest migration state from STOP to STOP_COPY Anthony Krowiak
2026-11-06 15:36 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 07/14] s390/vfio-ap: File ops called to save the vfio device migration state Anthony Krowiak
2026-11-06 15:45 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 08/14] s390/vfio-ap: Transition device migration state from STOP to RESUMING Anthony Krowiak
2026-11-06 15:40 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 09/14] s390/vfio-ap: File ops called to resume the vfio device migration Anthony Krowiak
2026-11-06 15:53 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 10/14] s390/vfio-ap: Transition device migration state to from/to STOP Anthony Krowiak
2026-11-06 15:51 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 11/14] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration Anthony Krowiak
2026-11-06 15:52 ` sashiko-bot
2026-11-06 15:22 ` Anthony Krowiak [this message]
2026-11-06 16:05 ` [PATCH v12 12/14] s390/vfio-ap: Set up for vfio-ap device migration sashiko-bot
2026-11-11 15:32 ` Anthony Krowiak
2026-11-06 15:22 ` [PATCH v12 13/14] s390/vfio-ap: Add 'migration' feature to sysfs 'features' attribute Anthony Krowiak
2026-11-06 16:04 ` sashiko-bot
2026-11-06 15:22 ` [PATCH v12 14/14] s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst Anthony Krowiak
2026-11-06 15:57 ` sashiko-bot
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=20261106152259.1360651-13-akrowiak@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=borntraeger@de.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.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 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.