From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Alex Williamson <alex@shazbot.org>,
Omar Elghoul <oelghoul@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, schnelle@linux.ibm.com, alifm@linux.ibm.com,
farman@linux.ibm.com, gbayer@linux.ibm.com, pasic@linux.ibm.com
Subject: Re: [PATCH v7 4/4] vfio-pci/zdev: Add VFIO FMB device features
Date: Wed, 30 Sep 2026 15:17:06 -0400 [thread overview]
Message-ID: <d85157b0-1574-4ac5-9fb4-9dc86c2530df@linux.ibm.com> (raw)
In-Reply-To: <20260930125750.7a5bc3a8@shazbot.org>
>> +#define VFIO_DEVICE_FEATURE_ZPCI_FMB_READ 15
>> +
>> +struct vfio_device_feature_zpci_fmb_read {
>> + __aligned_u64 data;
>> +};
>> +
>
> As usual, feature numbers need to be coordinated with the vfio tree.
> What's the merge plan for this? Thanks,
>
Looks like some s390 KVM maintainers weren't on CC, added Janosch and
Claudio (Omar please make sure to include them for next version)...
s390(-kvm) maintainers,
Do you think you would take this via s390-kvm (or s390) with Alex's ack
on the vfio parts, or vice versa? (Please note: this is not yet the
final version of this series)
For perspective, the changes are mostly in arch/s390 and the
s390-specific vfio_pci_zdev code.
s390 changes:
arch/s390/include/asm/pci.h | 2 +
arch/s390/pci/pci.c | 85 +++++++++++++++++++++++++-------
arch/s390/pci/pci_debug.c | 11 ++++-
drivers/vfio/pci/vfio_pci_zdev.c | 60 ++++++++++++++++++++++
VFIO changes:
drivers/vfio/pci/vfio_pci_core.c | 4 ++
drivers/vfio/pci/vfio_pci_priv.h | 18 +++++++
include/uapi/linux/vfio.h | 29 +++++++++++
Thanks,
Matt
next prev parent reply other threads:[~2026-09-30 19:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:51 [PATCH v7 0/4] vfio-pci/zdev: Improved zPCI Function Measurement Support Omar Elghoul
2026-09-22 19:51 ` [PATCH v7 1/4] s390/pci: Hold fmb_lock when enabling or disabling PCI devices Omar Elghoul
2026-09-22 19:51 ` [PATCH v7 2/4] s390/pci: Reuse FMB buffer and preserve state in device re-enablement Omar Elghoul
2026-09-23 15:09 ` Gerd Bayer
2026-09-23 16:37 ` Omar Elghoul
2026-09-24 15:55 ` Gerd Bayer
2026-09-24 16:47 ` Omar Elghoul
2026-09-23 22:20 ` Matthew Rosato
2026-09-24 14:27 ` Omar Elghoul
2026-09-30 18:57 ` Alex Williamson
2026-09-30 19:36 ` Omar Elghoul
2026-09-22 19:51 ` [PATCH v7 3/4] s390/pci: Fence FMB enable/disable via debugfs for passthrough devices Omar Elghoul
2026-09-22 19:51 ` [PATCH v7 4/4] vfio-pci/zdev: Add VFIO FMB device features Omar Elghoul
2026-09-30 18:57 ` Alex Williamson
2026-09-30 19:17 ` Matthew Rosato [this message]
2026-09-30 19:40 ` Omar Elghoul
2026-09-30 20:03 ` Alex Williamson
2026-09-30 17:48 ` [PATCH v7 0/4] vfio-pci/zdev: Improved zPCI Function Measurement Support Omar Elghoul
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=d85157b0-1574-4ac5-9fb4-9dc86c2530df@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oelghoul@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@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
all inboxes | Powered by JetHome®