From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Cornelia Huck <cohuck@redhat.com>
Subject: [Qemu-devel] [PULL 05/10] s390x/pci: mark zpci devices as unmigratable
Date: Tue, 5 Feb 2019 17:41:04 +0100 [thread overview]
Message-ID: <20190205164109.25413-6-cohuck@redhat.com> (raw)
In-Reply-To: <20190205164109.25413-1-cohuck@redhat.com>
We currently don't migrate any state for zpci devices, which are
coupled with standard pci devices. This means funny things happen
when we e.g. try to migrate with a virtio-pci device but the s390x-
specific zpci state is not migrated (vfio-pci is not affected, as
it is not migratable anyway.)
Until this is fixed, mark zpci devices as unmigratable.
Reported-by: David Hildenbrand <david@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Collin Walling <walling@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
hw/s390x/s390-pci-bus.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
index c96a7cba34..96c7c18f3f 100644
--- a/hw/s390x/s390-pci-bus.c
+++ b/hw/s390x/s390-pci-bus.c
@@ -1253,6 +1253,15 @@ static Property s390_pci_device_properties[] = {
DEFINE_PROP_END_OF_LIST(),
};
+static const VMStateDescription s390_pci_device_vmstate = {
+ .name = TYPE_S390_PCI_DEVICE,
+ /*
+ * TODO: add state handling here, so migration works at least with
+ * emulated pci devices on s390x
+ */
+ .unmigratable = 1,
+};
+
static void s390_pci_device_class_init(ObjectClass *klass, void *data)
{
DeviceClass *dc = DEVICE_CLASS(klass);
@@ -1263,6 +1272,7 @@ static void s390_pci_device_class_init(ObjectClass *klass, void *data)
dc->bus_type = TYPE_S390_PCI_BUS;
dc->realize = s390_pci_device_realize;
dc->props = s390_pci_device_properties;
+ dc->vmsd = &s390_pci_device_vmstate;
}
static const TypeInfo s390_pci_device_info = {
--
2.17.2
next prev parent reply other threads:[~2019-02-05 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 16:40 [Qemu-devel] [PULL 00/10] s390x update Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 01/10] target/s390x: define TCG_GUEST_DEFAULT_MO for MTTCG Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 02/10] s390x: remove direct reference to mem_path global from s390x code Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 03/10] s390x/pci: Introduce unplug requests and split unplug handler Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 04/10] s390x/pci: Drop release timer and replace it with a flag Cornelia Huck
2019-02-05 16:41 ` Cornelia Huck [this message]
2019-02-05 16:41 ` [Qemu-devel] [PULL 06/10] s390x/tcg: Don't model FP registers as globals Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 07/10] s390x/pci: Fix primary bus number for PCI bridges Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 08/10] s390x/pci: Fix hotplugging of " Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 09/10] s390x/pci: Warn when adding PCI devices without the 'zpci' feature Cornelia Huck
2019-02-05 16:41 ` [Qemu-devel] [PULL 10/10] s390x/pci: Unplug remaining requested devices on pcihost reset Cornelia Huck
2019-02-05 18:21 ` [Qemu-devel] [PULL 00/10] s390x update Peter Maydell
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=20190205164109.25413-6-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).