From: sashiko-bot@kernel.org
To: "Anthony Krowiak" <akrowiak@linux.ibm.com>
Cc: "Vasily Gorbik" <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
"Heiko Carstens" <hca@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v8 15/15] s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst
Date: Fri, 09 Oct 2026 11:53:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-165442@kernel.org> (raw)
In-Reply-To: <20261009114244.1213173-16-akrowiak@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] doc: vfio-ap: incorrect host reference in destination host configuration section
--
commit b9b160f01756abd52de1ef4f9e6032ef6704eaea
Author: Anthony Krowiak <akrowiak@linux.ibm.com>
s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst
Add a 'Live Guest Migration' chapter to the
Documentation/arch/s390/vfio-ap.rst document to describe the details for
initiating live guest migration for a guest to which AP adapters, domains
and control domains have been passed through.
> diff --git a/Documentation/arch/s390/vfio-ap.rst b/Documentation/arch/s390/vfio-ap.rst
> index ac0c07f76ddd7..02d7cbe5e4791 100644
> --- a/Documentation/arch/s390/vfio-ap.rst
> +++ b/Documentation/arch/s390/vfio-ap.rst
[ ... ]
> + * Display the AP configuration of the destination host with the following
> + two commands:
> +
> + .. code-block:: bash
> +
> + lszcrypt -V
> + cat /sys/bus/ap/ap_control_domain_mask
> +
> + .. note::
> + The ``lszcrypt -V`` command lists the AP cards (adapters) and queue
> + devices on the host system; for example:
> +
> + .. code-block:: bash
> +
> + =========== ===== ============ ==========
> + CARD.DOMAIN TYPE MODE DRIVER
> + =========== ===== ============ ==========
> + 00 CEX5C CCA-Coproc cex4card
> + 00.0033 CEX5C CCA-Coproc vfio_ap
> + 00.003a CEX5C CCA-Coproc vfio_ap
> + =========== ===== ============ ==========
> +
> + Each bit in the ap_control_domain_mask corresponds to
> + domain numbers 0-255. If a bit is set to one, then
> + the control domain is available on the source host. For
> + example:
[Severity: Low]
Does this mistakenly refer to the "source host" instead of the "destination
host"?
This section appears to be explaining the ap_control_domain_mask of the
destination host based on the commands above it, which display the
configuration for the destination host.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009114244.1213173-1-akrowiak@linux.ibm.com?part=15
prev parent reply other threads:[~2026-10-09 11:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 11:42 [PATCH v8 00/15] s390/vfio-ap: Add live guest migration support Anthony Krowiak
2026-10-09 11:42 ` [PATCH v8 01/15] s390/vfio-ap: Provide function to get the number of queues assigned to mdev Anthony Krowiak
2026-10-09 11:48 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 02/15] s390/vfio-ap: Data structures for facilitating vfio device migration Anthony Krowiak
2026-10-09 11:55 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 03/15] s390/vfio-ap: Functions to initialize/release vfio device migration data Anthony Krowiak
2026-10-09 11:52 ` sashiko-bot
2026-10-10 0:37 ` kernel test robot
2026-10-09 11:42 ` [PATCH v8 04/15] s390/vfio-ap: Reset migration state in VFIO_DEVICE_RESET ioctl handler Anthony Krowiak
2026-10-09 11:54 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 05/15] s390/vfio-ap: Callback to get/set vfio device mig state during guest migration Anthony Krowiak
2026-10-09 11:51 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 06/15] s390/vfio-ap: Transition guest migration state from STOP to STOP_COPY Anthony Krowiak
2026-10-09 11:57 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 07/15] s390/vfio-ap: File ops called to save the vfio device migration state Anthony Krowiak
2026-10-09 11:54 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 08/15] s390/vfio-ap: Transition device migration state from STOP to RESUMING Anthony Krowiak
2026-10-09 11:52 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 09/15] s390/vfio-ap: Prepare lock helpers and matrix init for cross-file use Anthony Krowiak
2026-10-09 11:51 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 10/15] s390/vfio-ap: Add method to set a new guest AP configuration Anthony Krowiak
2026-10-09 11:53 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 11/15] s390/vfio-ap: File ops called to resume the vfio device migration Anthony Krowiak
2026-10-09 11:56 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 12/15] s390/vfio-ap: Transition device migration state to from/to STOP Anthony Krowiak
2026-10-09 11:54 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 13/15] s390/vfio-ap: Callback to get the size of data to be migrated during guest migration Anthony Krowiak
2026-10-09 11:54 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 14/15] s390/vfio-ap: Add 'migratable' feature to sysfs 'features' attribute Anthony Krowiak
2026-10-09 11:56 ` sashiko-bot
2026-10-09 11:42 ` [PATCH v8 15/15] s390/vfio-ap: Add live guest migration chapter to vfio-ap.rst Anthony Krowiak
2026-10-09 11:53 ` sashiko-bot [this message]
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-165442@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=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox