From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Collin Walling <walling@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] s390x/pci: Unplug remaining devices on pcihost reset
Date: Wed, 23 Jan 2019 12:05:39 +0100 [thread overview]
Message-ID: <20190123120539.3ca367f9.cohuck@redhat.com> (raw)
In-Reply-To: <20190121134249.16615-3-david@redhat.com>
On Mon, 21 Jan 2019 14:42:49 +0100
David Hildenbrand <david@redhat.com> wrote:
> When resetting the guest we should unplug and remove all devices that
> are still pending. Otherwise the fresh guest will see devices that will
> suddenly vanish.
>
> Can be triggered e.g. via
> (hmp) device_add virtio-mouse-pci,id=test
> (hmp) stop
> (hmp) device_del test
> (hmp) system_reset
> (hmp) c
>
> The device will vanish after roughly 5 minutes. With this patch, the
> device will vanish on reboot (S390_RESET_EXTERNAL and S390_RESET_REIPL,
> which reset the pcihost bridge via qemu_devices_reset()). If we want
> these devices to vanish directly on any reset (S390_RESET_MODIFIED_CLEAR
> and S390_RESET_LOAD_NORMAL), we have to modify s390_machine_reset(). But
> I have the feeling that this should not be done for all reset types.
>
> This approach is similar to what's done for acpi PCI hotplug in
> acpi_pcihp_reset() -> acpi_pcihp_update() ->
> acpi_pcihp_update_hotplug_bus() -> acpi_pcihp_eject_slot().
>
> s390_pci_generate_plug_event()'s will still be generated, I guess this
> is not an issue (same thing could happen right now if the timer expires
> just after reset).
I'm wondering what the architecture says regarding those events -- can
someone with access to the documentation comment?
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> hw/s390x/s390-pci-bus.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index bc17a8cf65..b70ae25533 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -1102,6 +1102,14 @@ static void s390_pcihost_reset(DeviceState *dev)
> {
> S390pciState *s = S390_PCI_HOST_BRIDGE(dev);
> PCIBus *bus = s->parent_obj.bus;
> + S390PCIBusDevice *pbdev, *next;
> +
> + /* Unplug all pending devices that were requested to be released */
> + QTAILQ_FOREACH_SAFE(pbdev, &s->zpci_devs, link, next) {
> + if (pbdev->release_timer) {
> + s390_pcihost_timer_cb(pbdev);
> + }
> + }
>
> s->bus_no = 0;
> pci_for_each_device(bus, pci_bus_num(bus), s390_pci_enumerate_bridge, s);
next prev parent reply other threads:[~2019-01-23 11:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 13:42 [Qemu-devel] [PATCH v3 0/2] s390x/pci: hotplug handler fixes and reworks David Hildenbrand
2019-01-21 13:42 ` [Qemu-devel] [PATCH v3 1/2] s390x/pci: Introduce unplug requests and split unplug handler David Hildenbrand
2019-01-23 11:03 ` Cornelia Huck
2019-01-23 11:08 ` David Hildenbrand
2019-01-28 11:27 ` Cornelia Huck
2019-01-29 13:31 ` Pierre Morel
2019-01-29 15:14 ` David Hildenbrand
2019-01-29 16:54 ` Pierre Morel
2019-01-29 20:27 ` David Hildenbrand
2019-01-30 19:52 ` [Qemu-devel] [qemu-s390x] " Collin Walling
2019-01-31 9:31 ` David Hildenbrand
2019-01-21 13:42 ` [Qemu-devel] [PATCH v3 2/2] s390x/pci: Unplug remaining devices on pcihost reset David Hildenbrand
2019-01-23 11:05 ` Cornelia Huck [this message]
2019-01-28 11:28 ` Cornelia Huck
2019-01-29 0:09 ` [Qemu-devel] [qemu-s390x] " Collin Walling
2019-01-29 10:24 ` David Hildenbrand
2019-01-29 13:50 ` Pierre Morel
2019-01-29 15:11 ` David Hildenbrand
2019-01-29 16:50 ` Pierre Morel
2019-01-29 18:20 ` David Hildenbrand
2019-01-29 18:37 ` Cornelia Huck
2019-01-29 18:42 ` Collin Walling
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=20190123120539.3ca367f9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
/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).