From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: sashiko-reviews@lists.linux.dev
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
Jason Herne <jjherne@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
frankja@linux.ibm.com
Subject: Re: [PATCH v6 13/15] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration
Date: Thu, 30 Jul 2026 07:26:08 -0400 [thread overview]
Message-ID: <3a54b8bf-94ec-4069-b654-9f9b5d77839c@linux.ibm.com> (raw)
In-Reply-To: <20260727181947.66E251F000E9@smtp.kernel.org>
On 7/27/26 2:19 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Logic duplication for calculating the configuration size.
> --
>
> --- Patch [13]: [PATCH v6 13/15] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration ---
> commit f0e78a002713b19ca67967cef71fbd73dea59ee7
> Author: Anthony Krowiak <akrowiak@linux.ibm.com>
>
> s390/vfio-ap: Callback to get the size of data to be migrated during guest migration
>
> This commit adds the mandatory migration_get_data_size callback for VFIO
> migration support on the s390 vfio_ap driver. The callback calculates the
> estimated data length required to migrate the device's internal state.
>
>> diff --git a/drivers/s390/crypto/vfio_ap_migration.c b/drivers/s390/crypto/vfio_ap_migration.c
>> index 1c385908fc39b..8379cf8bbce89 100644
>> --- a/drivers/s390/crypto/vfio_ap_migration.c
>> +++ b/drivers/s390/crypto/vfio_ap_migration.c
>> @@ -1392,7 +1392,18 @@ static int vfio_ap_get_state(struct vfio_device *vdev,
>> static int vfio_ap_get_data_size(struct vfio_device *vdev,
>> unsigned long *stop_copy_length)
>> {
>> - return -EOPNOTSUPP;
>> + struct ap_matrix_mdev *matrix_mdev;
>> + size_t qinfo_sz;
>> + int num_queues;
>> +
>> + mutex_lock(&matrix_dev->mdevs_lock);
>> + matrix_mdev = container_of(vdev, struct ap_matrix_mdev, vdev);
>> + num_queues = vfio_ap_mdev_get_num_queues(&matrix_mdev->shadow_apcb);
>> + qinfo_sz = num_queues * sizeof(struct vfio_ap_queue_info);
>> + *stop_copy_length = qinfo_sz + sizeof(struct vfio_ap_config);
> [Severity: Low]
> Does this code manually duplicate the size calculation logic already present
> in the existing static helper vfio_ap_config_size() within this same file?
Yes, it does. The vfio_ap_get_data_size function will be modified to
call the
vfio_ap_config_size function to set *stop_copy_length.
>
> Additionally, since struct vfio_ap_config uses a trailing flexible array
> member for qinfo, would it be better to use the standard struct_size() macro
> to compute the total length instead of manual multiplication and addition?
struct_size(p, member, count) expects a pointer to the structure for which
the size is to be calculated, so this can not be used; however, I think the
struct_size_t
>
>> + mutex_unlock(&matrix_dev->mdevs_lock);
>> +
>> + return 0;
>> }
next prev parent reply other threads:[~2026-07-30 11:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 17:32 [PATCH v6 00/15] s390/vfio-ap: Add live guest migration support Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 01/15] s390/vfio-ap: Provide function to get the number of queues assigned to mdev Anthony Krowiak
2026-07-27 17:38 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 02/15] s390/vfio-ap: Data structures for facilitating vfio device migration Anthony Krowiak
2026-07-27 17:40 ` sashiko-bot
2026-08-04 10:39 ` Anthony Krowiak
2026-08-04 10:49 ` Anthony Krowiak
2026-08-04 19:57 ` Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 03/15] s390/vfio-ap: Functions to initialize/release vfio device migration data Anthony Krowiak
2026-07-27 17:48 ` sashiko-bot
2026-08-04 19:51 ` Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 04/15] s390/vfio-ap: Reset migration state in VFIO_DEVICE_RESET ioctl handler Anthony Krowiak
2026-07-27 17:52 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 05/15] s390-vfio-ap: Callback to get/set vfio device mig state during guest migration Anthony Krowiak
2026-07-27 17:59 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 06/15] s390/vfio-ap: Transition guest migration state from STOP to STOP_COPY Anthony Krowiak
2026-07-27 18:00 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 07/15] s390/vfio-ap: File ops called to save the vfio device migration state Anthony Krowiak
2026-07-27 18:02 ` sashiko-bot
2026-08-04 17:07 ` Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 08/15] s390/vfio-ap: Transition device migration state from STOP to RESUMING Anthony Krowiak
2026-07-27 18:14 ` sashiko-bot
2026-07-28 22:29 ` Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 09/15] s390/vfio-ap: Add method to set a new guest AP configuration Anthony Krowiak
2026-07-27 18:11 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 10/15] s390/vfio-ap: File ops called to resume the vfio device migration Anthony Krowiak
2026-07-27 18:12 ` sashiko-bot
2026-08-04 15:33 ` Anthony Krowiak
2026-07-27 17:32 ` [PATCH v6 11/15] s390/vfio-ap: Transition device migration state to STOP Anthony Krowiak
2026-07-27 18:26 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 12/15] s390/vfio-ap: Transition device migration state from STOP to RUNNING and vice versa Anthony Krowiak
2026-07-27 18:28 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 13/15] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration Anthony Krowiak
2026-07-27 18:19 ` sashiko-bot
2026-07-30 11:26 ` Anthony Krowiak [this message]
2026-07-27 17:32 ` [PATCH v6 14/15] s390/vfio-ap: Add 'migratable' feature to sysfs 'features' attribute Anthony Krowiak
2026-07-27 18:45 ` sashiko-bot
2026-07-27 17:32 ` [PATCH v6 15/15] s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst Anthony Krowiak
2026-07-27 18:27 ` 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=3a54b8bf-94ec-4069-b654-9f9b5d77839c@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox