On Wed, Jun 25, 2025 at 10:56:44AM +0200, Cédric Le Goater wrote:
> Could you please send v5 this week ? I plan to merge it first as other
> proposals are knocking at the VFIO door and I am OOO on week 28.
Will take care of your Error comments then send out
thanks
john
On 6/21/25 16:50, John Levon wrote:
On Sat, Jun 21, 2025 at 04:25:24PM +0200, Cédric Le Goater wrote:
So please let me know what if anything needs to be fixed (and if I should make
the same retrospective fix to hw/vfio/ equivalent).
Did you update the QEMU tree ?
$ git describe
v10.0.0
On Sat, Jun 21, 2025 at 04:25:24PM +0200, Cédric Le Goater wrote:
> > So please let me know what if anything needs to be fixed (and if I should
> > make
> > the same retrospective fix to hw/vfio/ equivalent).
>
> Did you update the QEMU tree ?
>
> $ git describe
> v10.0.0-1657-g6e1571533fd9
On 6/21/25 13:45, John Levon wrote:
On Fri, Jun 20, 2025 at 11:11:10AM +0200, Cédric Le Goater wrote:
The series contains an implement of a vfio-user client in QEMU, along with a few
more preparatory patches.
Please run ./scripts/checkpatch.pl and resend later on, as we might get
reviews.
O
On Fri, Jun 20, 2025 at 11:11:10AM +0200, Cédric Le Goater wrote:
> > The series contains an implement of a vfio-user client in QEMU, along with
> > a few
> > more preparatory patches.
>
> Please run ./scripts/checkpatch.pl and resend later on, as we might get
> reviews.
Output is below, MAINTA
On 6/19/25 15:31, 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
implementat
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
