From: "Cédric Le Goater" <clg@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: mjrosato@linux.ibm.com, thuth@redhat.com, alex.williamson@redhat.com
Subject: Re: [PATCH v2 4/4] s390x/pci: Reset a device in error state
Date: Mon, 1 Sep 2025 13:17:44 +0200 [thread overview]
Message-ID: <e3e6f261-4bc5-40f4-b3f9-65d2293e9276@redhat.com> (raw)
In-Reply-To: <20250825212434.2255-5-alifm@linux.ibm.com>
On 8/25/25 23:24, Farhan Ali wrote:
> For passthrough devices in error state, for a guest driven reset of the
> device we can attempt a reset to recover the device. A reset of the device
> will trigger a CLP disable/enable cycle on the host to bring the device
> into a recovered state.
>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 7 +++++++
> hw/s390x/s390-pci-vfio.c | 6 ++++++
> include/hw/s390x/s390-pci-vfio.h | 2 ++
> 3 files changed, 15 insertions(+)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index af42eb9938..c9c2d775f0 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -1493,6 +1493,8 @@ static void s390_pci_device_reset(DeviceState *dev)
> return;
> case ZPCI_FS_STANDBY:
> break;
> + case ZPCI_FS_ERROR:
> + break;
> default:
> pbdev->fh &= ~FH_MASK_ENABLE;
> pbdev->state = ZPCI_FS_DISABLED;
> @@ -1505,6 +1507,11 @@ static void s390_pci_device_reset(DeviceState *dev)
> } else if (pbdev->summary_ind) {
> pci_dereg_irqs(pbdev);
> }
> +
> + if (pbdev->state == ZPCI_FS_ERROR) {
> + s390_pci_reset(pbdev);
> + }
> +
> if (pbdev->iommu->enabled) {
> pci_dereg_ioat(pbdev->iommu);
> }
> diff --git a/hw/s390x/s390-pci-vfio.c b/hw/s390x/s390-pci-vfio.c
> index 87ecd06a81..a11ec770a7 100644
> --- a/hw/s390x/s390-pci-vfio.c
> +++ b/hw/s390x/s390-pci-vfio.c
> @@ -158,6 +158,12 @@ static void s390_pci_err_handler(VFIOPCIDevice *vfio_pci)
> return;
> }
>
> +void s390_pci_reset(S390PCIBusDevice *pbdev)
> +{
> + VFIOPCIDevice *vfio_pci = container_of(pbdev->pdev, VFIOPCIDevice, pdev);
> + ioctl(vfio_pci->vbasedev.fd, VFIO_DEVICE_RESET);
> +}
> +
> static void s390_pci_read_base(S390PCIBusDevice *pbdev,
> struct vfio_device_info *info)
> {
> diff --git a/include/hw/s390x/s390-pci-vfio.h b/include/hw/s390x/s390-pci-vfio.h
> index 66b274293c..c28dafeed8 100644
> --- a/include/hw/s390x/s390-pci-vfio.h
> +++ b/include/hw/s390x/s390-pci-vfio.h
> @@ -23,6 +23,7 @@ void s390_pci_end_dma_count(S390pciState *s, S390PCIDMACount *cnt);
> bool s390_pci_get_host_fh(S390PCIBusDevice *pbdev, uint32_t *fh);
> void s390_pci_get_clp_info(S390PCIBusDevice *pbdev);
> void s390_pci_setup_err_handler(S390PCIBusDevice *pbdev);
> +void s390_pci_reset(S390PCIBusDevice *pbdev);
> #else
> static inline bool s390_pci_update_dma_avail(int fd, unsigned int *avail)
> {
> @@ -41,6 +42,7 @@ static inline bool s390_pci_get_host_fh(S390PCIBusDevice *pbdev, uint32_t *fh)
> }
> static inline void s390_pci_get_clp_info(S390PCIBusDevice *pbdev) { }
> static inline void s390_pci_setup_err_handler(S390PCIBusDevice *pbdev) { }
> +void s390_pci_reset(S390PCIBusDevice *pbdev) { }
static inline void ... ^
Thanks,
C.
> #endif
>
> #endif
next prev parent reply other threads:[~2025-09-01 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 21:24 [PATCH v2 0/4] Error recovery for zPCI passthrough devices Farhan Ali
2025-08-25 21:24 ` [PATCH v2 1/4] [NOTFORMERGE] linux-headers: Update for zpci vfio device Farhan Ali
2025-08-25 21:24 ` [PATCH v2 2/4] vfio/pci: Add an architecture specific error handler Farhan Ali
2025-09-01 11:28 ` Cédric Le Goater
2025-09-03 16:49 ` Farhan Ali
2025-09-09 20:56 ` Cédric Le Goater
2025-08-25 21:24 ` [PATCH v2 3/4] s390x/pci: Add PCI error handling for vfio pci devices Farhan Ali
2025-09-01 11:25 ` Cédric Le Goater
2025-09-03 17:12 ` Farhan Ali
2025-09-03 17:49 ` Matthew Rosato
2025-09-09 7:59 ` Cédric Le Goater
2025-08-25 21:24 ` [PATCH v2 4/4] s390x/pci: Reset a device in error state Farhan Ali
2025-09-01 11:17 ` Cédric Le Goater [this message]
2025-09-03 17:13 ` Farhan Ali
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=e3e6f261-4bc5-40f4-b3f9-65d2293e9276@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).