From: Alex Williamson <alex.williamson@redhat.com>
To: robin@streamhpc.com, mst@redhat.com, marcel.apfelbaum@gmail.com
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, clg@redhat.com
Subject: [RFC PATCH v2 1/4] linux-headers: Update for vfio capability reporting AtomicOps
Date: Fri, 26 May 2023 17:15:55 -0600 [thread overview]
Message-ID: <20230526231558.1660396-2-alex.williamson@redhat.com> (raw)
In-Reply-To: <20230526231558.1660396-1-alex.williamson@redhat.com>
This is a partial linux-headers update for illustrative and testing
purposes only, NOT FOR COMMIT.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
| 14 ++++++++++++++
1 file changed, 14 insertions(+)
--git a/linux-headers/linux/vfio.h b/linux-headers/linux/vfio.h
index 4a534edbdcba..443a8851e156 100644
--- a/linux-headers/linux/vfio.h
+++ b/linux-headers/linux/vfio.h
@@ -240,6 +240,20 @@ struct vfio_device_info {
#define VFIO_DEVICE_INFO_CAP_ZPCI_UTIL 3
#define VFIO_DEVICE_INFO_CAP_ZPCI_PFIP 4
+/*
+ * The following VFIO_DEVICE_INFO capability reports support for PCIe AtomicOp
+ * completion to the root bus with supported widths provided via flags.
+ */
+#define VFIO_DEVICE_INFO_CAP_PCI_ATOMIC_COMP 5
+struct vfio_device_info_cap_pci_atomic_comp {
+ struct vfio_info_cap_header header;
+ __u32 flags;
+#define VFIO_PCI_ATOMIC_COMP32 (1 << 0)
+#define VFIO_PCI_ATOMIC_COMP64 (1 << 1)
+#define VFIO_PCI_ATOMIC_COMP128 (1 << 2)
+ __u32 reserved;
+};
+
/**
* VFIO_DEVICE_GET_REGION_INFO - _IOWR(VFIO_TYPE, VFIO_BASE + 8,
* struct vfio_region_info)
--
2.39.2
next prev parent reply other threads:[~2023-05-26 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:15 [RFC PATCH v2 0/4] vfio/pci: Atomic Ops completer support Alex Williamson
2023-05-26 23:15 ` Alex Williamson [this message]
2023-05-30 13:19 ` [RFC PATCH v2 1/4] linux-headers: Update for vfio capability reporting AtomicOps Cédric Le Goater
2023-05-26 23:15 ` [RFC PATCH v2 2/4] vfio: Implement a common device info helper Alex Williamson
2023-05-31 10:18 ` Robin Voetter
2023-05-26 23:15 ` [RFC PATCH v2 3/4] pcie: Add a PCIe capability version helper Alex Williamson
2023-05-30 12:30 ` Cédric Le Goater
2023-05-31 22:02 ` Robin Voetter
2023-05-31 22:19 ` Philippe Mathieu-Daudé
2023-05-26 23:15 ` [RFC PATCH v2 4/4] vfio/pci: Enable AtomicOps completers on root ports Alex Williamson
2023-05-30 13:36 ` Cédric Le Goater
2023-05-31 22:03 ` Robin Voetter
2023-05-31 22:28 ` Philippe Mathieu-Daudé
2023-05-31 21:55 ` [RFC PATCH v2 0/4] vfio/pci: Atomic Ops completer support Robin Voetter
2023-05-31 22:24 ` Alex Williamson
2023-05-31 22:29 ` Philippe Mathieu-Daudé
2023-06-02 14:02 ` Philippe Mathieu-Daudé
2023-06-01 8:15 ` Robin Voetter
2023-05-31 22:31 ` Philippe Mathieu-Daudé
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=20230526231558.1660396-2-alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robin@streamhpc.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).