qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: John Levon <john.levon@nutanix.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Thanos Makatos" <thanos.makatos@nutanix.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>
Subject: Re: [PATCH v3 00/23] vfio-user client
Date: Thu, 12 Jun 2025 08:57:54 +0200	[thread overview]
Message-ID: <b6be1ca0-0ba0-4691-8a2c-f7d3ddc2f85e@redhat.com> (raw)
In-Reply-To: <20250607001056.335310-1-john.levon@nutanix.com>

John,

On 6/7/25 02:10, John Levon wrote:
> The series contains an implement of a vfio-user client in QEMU, along with a few
> more preparatory patches.
> 
> The vfio-user protocol allows for implementing (PCI) devices in another
> userspace process; SPDK is one example, which includes a virtual NVMe
> implementation.
> 
> The vfio-user framework consists of 3 parts:
>   1) The VFIO user protocol specification.
>   2) A client - the VFIO device in QEMU that encapsulates VFIO messages
>      and sends them to the server.
>   3) A server - a remote process that emulates a device.
> 
> This patchset implements parts 1 and 2.
> 
> It has been tested against libvfio-user test servers as well as SPDK.

Is libvfio-user a server-only library ? It seems a bit odd not to use it
on the client side. Anyhow,


We have now merged upstream all the prerequisite changes for vfio-user.
This gives us about 1 month to fix regressions and merge the model for
the vfio-user-pci device, its documentation and tests.


I *really* would prefer if we had functional tests although I don't how
complex it would be. At least an initial framework would be good to have.
More sophisticated scenarios, such as mappings and interrupts, can come
later.

Thanks,

C.



  parent reply	other threads:[~2025-06-12  6:58 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-07  0:10 [PATCH v3 00/23] vfio-user client John Levon
2025-06-07  0:10 ` [PATCH v3 01/23] vfio: export PCI helpers needed for vfio-user John Levon
2025-06-10  7:00   ` Cédric Le Goater
2025-06-10 10:47   ` Mark Cave-Ayland
2025-06-10 17:38   ` Cédric Le Goater
2025-06-07  0:10 ` [PATCH v3 02/23] vfio: enable per-IRQ MSI-X masking John Levon
2025-06-10  7:27   ` Cédric Le Goater
2025-06-10 21:52   ` John Levon
2025-06-11  7:13     ` Cédric Le Goater
2025-06-07  0:10 ` [PATCH v3 03/23] vfio: add per-region fd support John Levon
2025-06-10  7:42   ` Cédric Le Goater
2025-06-10 12:34     ` John Levon
2025-06-11  7:12       ` Cédric Le Goater
2025-06-10 16:59     ` John Levon
2025-06-10 18:15     ` John Levon
2025-06-10 10:58   ` Mark Cave-Ayland
2025-06-10 11:27     ` John Levon
2025-06-10 11:57       ` Cédric Le Goater
2025-06-10 12:13         ` John Levon
2025-06-11  7:24   ` Cédric Le Goater
2025-06-07  0:10 ` [PATCH v3 04/23] vfio: mark posted writes in region write callbacks John Levon
2025-06-11  7:24   ` Cédric Le Goater
2025-06-07  0:10 ` [PATCH v3 05/23] vfio-user: introduce vfio-user protocol specification John Levon
2025-06-10  9:38   ` Cédric Le Goater
2025-06-10  9:55     ` John Levon
2025-06-10 10:12       ` Cédric Le Goater
2025-06-10 10:22         ` Mark Cave-Ayland
2025-06-10 13:06           ` Cédric Le Goater
2025-06-10 16:55     ` John Levon
2025-06-11 11:49   ` Cédric Le Goater
2025-06-07  0:10 ` [PATCH v3 06/23] vfio-user: add vfio-user class and container John Levon
2025-06-10  9:57   ` Cédric Le Goater
2025-06-10 16:52     ` John Levon
2025-06-11  7:46       ` Cédric Le Goater
2025-06-11  8:58         ` John Levon
2025-06-10 11:42   ` Mark Cave-Ayland
2025-06-10 11:56     ` John Levon
2025-06-10 12:15       ` Cédric Le Goater
2025-06-10 12:13     ` Cédric Le Goater
2025-06-12  6:39   ` Cédric Le Goater
2025-06-12 14:02     ` John Levon
2025-06-07  0:10 ` [PATCH v3 07/23] vfio-user: connect vfio proxy to remote server John Levon
2025-06-07  0:10 ` [PATCH v3 08/23] vfio-user: implement message receive infrastructure John Levon
2025-06-07  0:10 ` [PATCH v3 09/23] vfio-user: implement message send infrastructure John Levon
2025-06-07  0:10 ` [PATCH v3 10/23] vfio-user: implement VFIO_USER_DEVICE_GET_INFO John Levon
2025-06-07  0:10 ` [PATCH v3 11/23] vfio-user: implement VFIO_USER_DEVICE_GET_REGION_INFO John Levon
2025-06-07  0:10 ` [PATCH v3 12/23] vfio-user: implement VFIO_USER_REGION_READ/WRITE John Levon
2025-06-07  0:10 ` [PATCH v3 13/23] vfio-user: set up PCI in vfio_user_pci_realize() John Levon
2025-06-07  0:10 ` [PATCH v3 14/23] vfio-user: implement VFIO_USER_DEVICE_GET/SET_IRQ* John Levon
2025-06-07  0:10 ` [PATCH v3 15/23] vfio-user: forward MSI-X PBA BAR accesses to server John Levon
2025-06-07  0:10 ` [PATCH v3 16/23] vfio-user: set up container access to the proxy John Levon
2025-06-07  0:10 ` [PATCH v3 17/23] vfio-user: implement VFIO_USER_DEVICE_RESET John Levon
2025-06-07  0:10 ` [PATCH v3 18/23] vfio-user: implement VFIO_USER_DMA_MAP/UNMAP John Levon
2025-06-07  0:10 ` [PATCH v3 19/23] vfio-user: implement VFIO_USER_DMA_READ/WRITE John Levon
2025-06-07  0:10 ` [PATCH v3 20/23] vfio-user: add 'x-msg-timeout' option John Levon
2025-06-07  0:10 ` [PATCH v3 21/23] vfio-user: support posted writes John Levon
2025-06-07  0:10 ` [PATCH v3 22/23] vfio-user: add coalesced " John Levon
2025-06-07  0:10 ` [PATCH v3 23/23] docs: add vfio-user documentation John Levon
2025-06-12  6:57 ` Cédric Le Goater [this message]
2025-06-12 14:19   ` [PATCH v3 00/23] vfio-user client John Levon
2025-06-19 11:56     ` Cédric Le Goater
2025-06-20  8:20       ` Mark Cave-Ayland
2025-06-20  8:32         ` Cédric Le Goater
2025-06-21 12:22           ` John Levon
2025-06-22 12:57             ` Cédric Le Goater
2025-06-23  8:36               ` John Levon
2025-06-23 16:14                 ` Mark Cave-Ayland
2025-06-23 16:09               ` Mark Cave-Ayland
2025-06-23 17:06                 ` Cédric Le Goater

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=b6be1ca0-0ba0-4691-8a2c-f7d3ddc2f85e@redhat.com \
    --to=clg@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=berrange@redhat.com \
    --cc=john.levon@nutanix.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thanos.makatos@nutanix.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).