From: Farhan Ali <alifm@linux.ibm.com>
To: Niklas Schnelle <schnelle@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, mjrosato@linux.ibm.com
Subject: Re: [PATCH v14 5/7] vfio-pci/zdev: Add a device feature for error information
Date: Wed, 29 Apr 2026 09:59:03 -0700 [thread overview]
Message-ID: <19f8ffeb-9200-4f94-88bf-34b5cfa8b7d0@linux.ibm.com> (raw)
In-Reply-To: <56bcc0f67c15ad01f6fff161164698f1689af0f1.camel@linux.ibm.com>
On 4/29/2026 2:40 AM, Niklas Schnelle wrote:
>> +struct vfio_device_feature_zpci_err {
>> + __u32 flags; /* Indicate feature in non CCDF reserved space */
> The "non CCDF" feels a bit subtle for marking this as a vfio-pci
> feature specific field. Maybe call it "vfio_feat_flags"?
I was a little hesitant about naming it with vfio as it's not exactly
tied to anything in vfio framework. But if you feel strongly will change it.
>> + __u32 reserved1;
>> + __u32 fh; /* function handle */
>> + __u32 fid; /* function id */
>> + __u32 ett : 4; /* expected table type */
>> + __u32 mvn : 12; /* MSI vector number */
>> + __u32 dmaas : 8; /* DMA address space */
>> + __u32 reserved2 : 6;
>> + __u32 q : 1; /* event qualifier */
>> + __u32 rw : 1; /* read/write */
>> + __u64 faddr; /* failing address */
>> + __u32 reserved3;
>> + __u16 reserved4;
>> + __u16 pec; /* PCI event code */
>> + __u8 reserved5[28]; /* Non CCDF reserved space */
> While also vfio-pci specific for now, the reserved5 would potentially
> become CCDF if that ever grows. Maybe the comment could say "Allow for
> future expansion"?
>
>
Sure, will update the comment.
Thanks
Farhan
next prev parent reply other threads:[~2026-04-29 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 16:30 [PATCH v14 0/7] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-04-21 16:30 ` [PATCH v14 1/7] PCI: Allow per function PCI slots to fix slot reset on s390 Farhan Ali
2026-04-21 16:30 ` [PATCH v14 2/7] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-04-21 16:30 ` [PATCH v14 3/7] PCI: Fail FLR when config space is inaccessible Farhan Ali
2026-04-21 16:30 ` [PATCH v14 4/7] s390/pci: Store PCI error information for passthrough devices Farhan Ali
2026-04-29 11:41 ` Niklas Schnelle
2026-04-29 16:48 ` Farhan Ali
2026-04-30 7:48 ` Niklas Schnelle
2026-04-30 16:44 ` Farhan Ali
2026-04-21 16:30 ` [PATCH v14 5/7] vfio-pci/zdev: Add a device feature for error information Farhan Ali
2026-04-29 9:40 ` Niklas Schnelle
2026-04-29 16:59 ` Farhan Ali [this message]
2026-04-30 8:35 ` Niklas Schnelle
2026-04-21 16:30 ` [PATCH v14 6/7] vfio/pci: Add a reset_done callback for vfio-pci driver Farhan Ali
2026-04-21 16:30 ` [PATCH v14 7/7] vfio/pci: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX Farhan Ali
2026-04-28 18:30 ` [PATCH v14 0/7] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-04-28 22:01 ` Bjorn Helgaas
2026-04-29 17:02 ` 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=19f8ffeb-9200-4f94-88bf-34b5cfa8b7d0@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=clg@redhat.com \
--cc=helgaas@kernel.org \
--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 \
/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