qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clegoate@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
	robin@streamhpc.com, mst@redhat.com, marcel.apfelbaum@gmail.com
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 1/4] linux-headers: Update for vfio capability reporting AtomicOps
Date: Mon, 3 Jul 2023 18:23:41 +0200	[thread overview]
Message-ID: <a6f961c2-803d-3979-a767-63d2e1f494c4@redhat.com> (raw)
In-Reply-To: <20230519215739.402729-2-alex.williamson@redhat.com>

On 5/19/23 23:57, Alex Williamson wrote:
> 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>
> ---
I am preparing a vfio-next tree including these changes plus a linux-headers
update. I am just waiting for the 6.5-rc1 tag to be pushed.

Thanks,

C.

>   linux-headers/linux/vfio.h | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
> 
> diff --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)



  reply	other threads:[~2023-07-03 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 21:57 [RFC PATCH 0/4] vfio/pci: Atomic Ops completer support Alex Williamson
2023-05-19 21:57 ` [RFC PATCH 1/4] linux-headers: Update for vfio capability reporting AtomicOps Alex Williamson
2023-07-03 16:23   ` Cédric Le Goater [this message]
2023-05-19 21:57 ` [RFC PATCH 2/4] vfio: Implement a common device info helper Alex Williamson
2023-05-20  4:33   ` Philippe Mathieu-Daudé
2023-05-22  7:19   ` Cédric Le Goater
2023-05-19 21:57 ` [RFC PATCH 3/4] pcie: Add a PCIe capability version helper Alex Williamson
2023-05-19 21:57 ` [RFC PATCH 4/4] vfio/pci: Enable AtomicOps completers on root ports Alex Williamson

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=a6f961c2-803d-3979-a767-63d2e1f494c4@redhat.com \
    --to=clegoate@redhat.com \
    --cc=alex.williamson@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).