From: Farhan Ali <alifm@linux.ibm.com>
To: Julian Ruess <julianr@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: helgaas@kernel.org, lukas@wunner.de, alex@shazbot.org,
clg@redhat.com, stable@vger.kernel.org, schnelle@linux.ibm.com,
mjrosato@linux.ibm.com
Subject: Re: [PATCH v7 7/9] vfio-pci/zdev: Add a device feature for error information
Date: Tue, 20 Jan 2026 10:54:48 -0800 [thread overview]
Message-ID: <af49850b-4c83-4847-a11f-deb864e4c691@linux.ibm.com> (raw)
In-Reply-To: <DFSPESVR3INE.HYERH8O05PYP@linux.ibm.com>
On 1/19/2026 8:24 AM, Julian Ruess wrote:
>> For zPCI devices, we have platform specific error information. The platform
>> firmware provides this error information to the operating system in an
>> architecture specific mechanism. To enable recovery from userspace for
>> these devices, we want to expose this error information to userspace. Add a
>> new device feature to expose this information.
>>
>> Signed-off-by: Farhan Ali<alifm@linux.ibm.com>
>> ---
>> drivers/vfio/pci/vfio_pci_core.c | 2 ++
>> drivers/vfio/pci/vfio_pci_priv.h | 9 +++++++++
>> drivers/vfio/pci/vfio_pci_zdev.c | 34 ++++++++++++++++++++++++++++++++
>> include/uapi/linux/vfio.h | 16 +++++++++++++++
>> 4 files changed, 61 insertions(+)
>>
>> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
>> index 3a11e6f450f7..f677705921e6 100644
>> --- a/drivers/vfio/pci/vfio_pci_core.c
>> +++ b/drivers/vfio/pci/vfio_pci_core.c
>> @@ -1526,6 +1526,8 @@ int vfio_pci_core_ioctl_feature(struct vfio_device *device, u32 flags,
>> return vfio_pci_core_feature_token(vdev, flags, arg, argsz);
>> case VFIO_DEVICE_FEATURE_DMA_BUF:
>> return vfio_pci_core_feature_dma_buf(vdev, flags, arg, argsz);
>> + case VFIO_DEVICE_FEATURE_ZPCI_ERROR:
>> + return vfio_pci_zdev_feature_err(device, flags, arg, argsz);
> Would it make sense to name this more generically, e.g.
> VFIO_DEVICE_FEATURE_ERROR_RECOVERY, in case other architectures also want to
> support something like this in the future?
The error recovery mechanism here and also the uapi structure exposed
via this device feature is very specific to zPCI devices. Making this a
generic device feature would mean having different uapi structure for
zPCI devices vs PCI devices on other architectures. I am not sure that
would be desirable and might be cleaner to have separate device feature
and separate uapi constructs for zPCI vs other architectures.
Thanks
Farhan
next prev parent reply other threads:[~2026-01-20 18:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 18:32 [PATCH v7 0/9] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-01-07 18:32 ` [PATCH v7 1/9] PCI: Allow per function PCI slots Farhan Ali
2026-01-07 18:32 ` [PATCH v7 2/9] s390/pci: Add architecture specific resource/bus address translation Farhan Ali
2026-01-20 22:15 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 3/9] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-01-19 21:23 ` Niklas Schnelle
2026-01-20 19:50 ` Farhan Ali
2026-01-20 22:12 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 4/9] PCI: Add additional checks for flr reset Farhan Ali
2026-01-19 21:34 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 5/9] s390/pci: Update the logic for detecting passthrough device Farhan Ali
2026-01-07 18:32 ` [PATCH v7 6/9] s390/pci: Store PCI error information for passthrough devices Farhan Ali
2026-01-20 22:34 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 7/9] vfio-pci/zdev: Add a device feature for error information Farhan Ali
2026-01-19 16:24 ` Julian Ruess
2026-01-20 18:54 ` Farhan Ali [this message]
2026-01-07 18:32 ` [PATCH v7 8/9] vfio: Add a reset_done callback for vfio-pci driver Farhan Ali
2026-01-19 16:41 ` Julian Ruess
2026-01-07 18:32 ` [PATCH v7 9/9] vfio: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX Farhan Ali
2026-01-19 16:56 ` Julian Ruess
2026-01-20 18:56 ` Farhan Ali
2026-01-15 18:28 ` [PATCH v7 0/9] Error recovery for vfio-pci devices on s390x 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=af49850b-4c83-4847-a11f-deb864e4c691@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=clg@redhat.com \
--cc=helgaas@kernel.org \
--cc=julianr@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjrosato@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®