From: Thomas Huth <thuth@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>, qemu-s390x@nongnu.org
Cc: farman@linux.ibm.com, pasic@linux.ibm.com,
borntraeger@linux.ibm.com, richard.henderson@linaro.org,
david@redhat.com, iii@linux.ibm.com, clg@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] s390x/pci: fix cleanup of failed hotplug
Date: Wed, 5 Mar 2025 15:35:13 +0100 [thread overview]
Message-ID: <393fdd69-69b9-4d10-8a08-834f0aa82978@redhat.com> (raw)
In-Reply-To: <20250226210201.238489-2-mjrosato@linux.ibm.com>
On 26/02/2025 22.02, Matthew Rosato wrote:
> In the unlikely event that we must fail hotplug of a PCI passthrough
> device, ensure appropriate clean up of the associated zPCI device is
> performed.
>
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index 913d72cc74..6cc0e7538a 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -1119,7 +1119,7 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> if (rc) {
> error_setg(errp, "Plug failed for zPCI device in "
> "interpretation mode: %d", rc);
> - return;
> + goto pbdev_cleanup;
> }
> } else {
> trace_s390_pcihost("zPCI interpretation missing");
> @@ -1150,7 +1150,7 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> if (s390_pci_msix_init(pbdev) && !pbdev->interp) {
> error_setg(errp, "MSI-X support is mandatory "
> "in the S390 architecture");
> - return;
> + goto pbdev_cleanup;
> }
>
> if (dev->hotplugged) {
> @@ -1168,6 +1168,23 @@ static void s390_pcihost_plug(HotplugHandler *hotplug_dev, DeviceState *dev,
> } else {
> g_assert_not_reached();
> }
> +
> + return;
> +
> + pbdev_cleanup:
> + DeviceState *bdev = DEVICE(pbdev);
> +
> + if (pbdev->shutdown_notifier.notify) {
> + notifier_remove(&pbdev->shutdown_notifier);
> + }
> + if (pbdev->iommu->dma_limit) {
> + s390_pci_end_dma_count(s, pbdev->iommu->dma_limit);
> + }
> + s390_pci_iommu_free(s, pci_get_bus(pbdev->pdev), pbdev->pdev->devfn);
> + QTAILQ_REMOVE(&s->zpci_devs, pbdev, link);
> + g_hash_table_remove(s->zpci_table, &pbdev->idx);
> + object_unparent(OBJECT(bdev));
> + qdev_unrealize(bdev);
> }
Not sure, but should bdev realy be unrealized here already? Or should that
rather be done by the caller (when it sees the errp set)?
Thomas
next prev parent reply other threads:[~2025-03-05 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 21:01 [PATCH 0/2] s390x/pci: changes to hotplug error handling Matthew Rosato
2025-02-26 21:02 ` [PATCH 1/2] s390x/pci: fix cleanup of failed hotplug Matthew Rosato
2025-03-05 14:35 ` Thomas Huth [this message]
2025-02-26 21:02 ` [PATCH 2/2] s390x/pci: add message for ISM without zPCI interpretation Matthew Rosato
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=393fdd69-69b9-4d10-8a08-834f0aa82978@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=david@redhat.com \
--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 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).