From: sashiko-bot@kernel.org
To: "Anthony Krowiak" <akrowiak@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v12 06/14] s390/vfio-ap: Transition guest migration state from STOP to STOP_COPY
Date: Fri, 06 Nov 2026 15:36:12 +0000 [thread overview]
Message-ID: <sashiko-outbox-201704@kernel.org> (raw)
In-Reply-To: <20261106152259.1360651-7-akrowiak@linux.ibm.com>
> The transition of the guest migration state from VFIO_DEVICE_STATE_STOP to
> VFIO_DEVICE_STATE_STOP_COPY begins the process of saving the
> vfio device state. The vfio device state is comprised of the guest's
> AP configuration which specifies the adapters, domains and control
> domains to which the guest will be given access.
>
> To begin the process of saving the vfio device state, the VFIO AP device
> driver opens a file stream that will be used to read the source guest's
> AP configuration.
>
> Note:
> This commit introduces the file operations structure for migration state
> files with a stub implementation of the read operation. The complete
> implementation is provided in the subsequent commit.
>
> This incremental approach allows for easier review of the migration
> infrastructure setup separate from the actual implementation logic.
>
> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106152259.1360651-1-akrowiak@linux.ibm.com?part=6
next prev parent reply other threads:[~2026-11-06 15:36 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 [this message]
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 ` [PATCH v12 12/14] s390/vfio-ap: Set up for vfio-ap device migration Anthony Krowiak
2026-11-06 16:05 ` 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=sashiko-outbox-201704@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.