All of lore.kernel.org
 help / color / mirror / Atom feed
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 v13 03/14] s390/vfio-ap: Functions to initialize/release vfio device migration data
Date: Wed, 11 Nov 2026 20:21:49 +0000	[thread overview]
Message-ID: <sashiko-outbox-209642@kernel.org> (raw)
In-Reply-To: <20261111192308.2585984-4-akrowiak@linux.ibm.com>

> Provides the functions that initialize and release the data structures
> used during live guest migration:
> 
> * vfio_ap_init_migration_data
> 
>   Allocates and initializes the object used to maintain the state of the
>   VFIO migration. It is called when the VFIO device is opened and does
>   nothing if the object was allocated by a previous open.
> 
> * vfio_ap_release_migration_data
> 
>   Frees the memory of the object used to maintain the VFIO migration
>   state. It is called only from the VFIO device release callback. It is
>   not called when the VFIO device is closed because a migration file
>   descriptor, which references the object, can outlive the VFIO device
> [ ... ]
>   pointer in, the vfio_ap_migration_file used during the RESUMING phase
>   of migration. It also clears the flag indicating a complete AP
>   configuration was received.
> 
> 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/20261111192308.2585984-1-akrowiak@linux.ibm.com?part=3


  reply	other threads:[~2026-11-11 20:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 19:22 [PATCH v13 00/14] s390/vfio-ap: Add live guest migration support Anthony Krowiak
2026-11-11 19:22 ` [PATCH v13 01/14] s390/vfio-ap: Provide function to get the number of queues assigned to mdev Anthony Krowiak
2026-11-11 20:12   ` sashiko-bot
2026-11-11 19:22 ` [PATCH v13 02/14] s390/vfio-ap: Data structures for facilitating vfio device migration Anthony Krowiak
2026-11-11 20:12   ` sashiko-bot
2026-11-11 19:22 ` [PATCH v13 03/14] s390/vfio-ap: Functions to initialize/release vfio device migration data Anthony Krowiak
2026-11-11 20:21   ` sashiko-bot [this message]
2026-11-11 19:22 ` [PATCH v13 04/14] s390/vfio-ap: Reset migration state on VFIO_DEVICE_RESET and device close Anthony Krowiak
2026-11-11 20:16   ` sashiko-bot
2026-11-11 19:22 ` [PATCH v13 05/14] s390/vfio-ap: Callback to get/set vfio device mig state during guest migration Anthony Krowiak
2026-11-11 20:20   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 06/14] s390/vfio-ap: Transition guest migration state from STOP to STOP_COPY Anthony Krowiak
2026-11-11 20:12   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 07/14] s390/vfio-ap: File ops called to save the vfio device migration state Anthony Krowiak
2026-11-11 20:15   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 08/14] s390/vfio-ap: Transition device migration state from STOP to RESUMING Anthony Krowiak
2026-11-11 20:17   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 09/14] s390/vfio-ap: File ops called to resume the vfio device migration Anthony Krowiak
2026-11-11 20:24   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 10/14] s390/vfio-ap: Transition device migration state to from/to STOP Anthony Krowiak
2026-11-11 20:18   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 11/14] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration Anthony Krowiak
2026-11-11 20:21   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 12/14] s390/vfio-ap: Set up for vfio-ap device migration Anthony Krowiak
2026-11-11 20:36   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 13/14] s390/vfio-ap: Add 'migration' feature to sysfs 'features' attribute Anthony Krowiak
2026-11-11 20:30   ` sashiko-bot
2026-11-11 19:23 ` [PATCH v13 14/14] s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst Anthony Krowiak
2026-11-11 20:21   ` 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-209642@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.