From: Konstantin Shkolnyy <kshk@linux.ibm.com>
To: mjrosato@linux.ibm.com
Cc: alifm@linux.ibm.com, farman@linux.ibm.com,
richard.henderson@linaro.org, iii@linux.ibm.com,
david@kernel.org, cohuck@redhat.com, pasic@linux.ibm.com,
borntraeger@linux.ibm.com, qemu-s390x@nongnu.org,
qemu-devel@nongnu.org, Konstantin Shkolnyy <kshk@linux.ibm.com>
Subject: [PATCH v12 00/17] s390x/pci: Implement migration for emulated devices
Date: Mon, 5 Oct 2026 19:16:26 -0500 [thread overview]
Message-ID: <20261006001643.420929-1-kshk@linux.ibm.com> (raw)
ATTENTION! This series is built to apply on top of https://gitlab.com/efarman/qemu/-/tree/s390-next.
Up until now QEMU marked any zPCI device as "unmigratable."
This patch series adds support for migrating emulated devices, which are
simpler to migrate. It leaves VFIO devices still unmigratable.
To enable migration, the device state needs to be saved/restored to/from
the migration stream.
There are 2 kinds of emulated devices - those that use the zPCI IOMMU page
table emulation in QEMU (e.g., Intel IGB NIC), and those that don't (virtio).
This is important to note for testing purposes.
This change was tested on IGB, virtio-net and virtio-blk devices by running
I/O on them while performing "virsh managedsave, virsh start" and also live
migration to another host and back.
Changes in v12:
- patch 14: Add a message to an error path that didn't have it.
- patch 15: New. Extract here an isolated change from the next patch to make it smaller.
- patch 16 (formerly 15):
- Simplify error handling on s390_pci_ioat_validate() failure,
- Put an assert() with a comment into unreacheable branch.
Konstantin Shkolnyy (16):
s390x/pci: Create function to contain translation status check
s390x/pci: Move iommu_mr from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move dm_mr from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move iotlb from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Remove a ptr to S390PCIBusDevice from S390PCIIOMMU
s390x/pci: Move/rename enabled from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move dma_limit from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move g_iota from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move pba from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move pal from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Move max_dma_limit from S390PCIIOMMU to S390PCIBusDevice
s390x/pci: Add a comment explaining S390PCIIOMMU purpose
s390x/pci: Move ioat sanity checks into new function, add error
message
s390x/pci: Provide each zpci device with a unique stable bus "path"
s390x/pci: Implement migration for emulated devices
s390x/pci: Create function to contain fmb_timer start
Matthew Rosato (1):
s390x/pci: implement IOMMU replay
hw/s390x/s390-pci-bus.c | 528 +++++++++++++++++++++++++++----
hw/s390x/s390-pci-inst.c | 174 +++++-----
hw/s390x/s390-pci-vfio.c | 4 +-
hw/s390x/s390-virtio-ccw.c | 4 +
include/hw/s390x/s390-pci-bus.h | 43 ++-
include/hw/s390x/s390-pci-inst.h | 7 +-
6 files changed, 611 insertions(+), 149 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-06 0:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 0:16 Konstantin Shkolnyy [this message]
2026-10-06 0:16 ` [PATCH v12 01/17] s390x/pci: implement IOMMU replay Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 02/17] s390x/pci: Create function to contain translation status check Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 03/17] s390x/pci: Move iommu_mr from S390PCIIOMMU to S390PCIBusDevice Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 04/17] s390x/pci: Move dm_mr " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 05/17] s390x/pci: Move iotlb " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 06/17] s390x/pci: Remove a ptr to S390PCIBusDevice from S390PCIIOMMU Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 07/17] s390x/pci: Move/rename enabled from S390PCIIOMMU to S390PCIBusDevice Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 08/17] s390x/pci: Move dma_limit " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 09/17] s390x/pci: Move g_iota " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 10/17] s390x/pci: Move pba " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 11/17] s390x/pci: Move pal " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 12/17] s390x/pci: Move max_dma_limit " Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 13/17] s390x/pci: Add a comment explaining S390PCIIOMMU purpose Konstantin Shkolnyy
2026-10-06 0:16 ` [PATCH v12 14/17] s390x/pci: Move ioat sanity checks into new function, add error message Konstantin Shkolnyy
2026-10-06 16:45 ` Matthew Rosato
2026-10-06 0:16 ` [PATCH v12 15/17] s390x/pci: Provide each zpci device with a unique stable bus "path" Konstantin Shkolnyy
2026-10-06 16:48 ` Matthew Rosato
2026-10-06 20:13 ` Farhan Ali
2026-10-06 0:16 ` [PATCH v12 16/17] s390x/pci: Implement migration for emulated devices Konstantin Shkolnyy
2026-10-06 20:35 ` Matthew Rosato
2026-10-06 21:13 ` Farhan Ali
2026-10-06 0:16 ` [PATCH v12 17/17] s390x/pci: Create function to contain fmb_timer start Konstantin Shkolnyy
2026-10-07 17:35 ` [PATCH v12 00/17] s390x/pci: Implement migration for emulated devices Eric Farman
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=20261006001643.420929-1-kshk@linux.ibm.com \
--to=kshk@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
/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.