> -Original Message-
> From: John Johnson
> Sent: 16 February 2022 02:10
> To: Thanos Makatos
> Cc: qemu-devel@nongnu.org
> Subject: Re: [RFC v4 08/21] vfio-user: define socket receive functions
>
>
>
> > On Feb 15, 2022, at
> On Feb 15, 2022, at 6:50 AM, Thanos Makatos
> wrote:
>
>>>
>
> On second thought, should we dump the entire header in case of such errors?
> If not by default then at least in debug builds?
I was thinking of adding qemu tracepoints in the recv and send paths
for your other
> > +/*
> > + * Receive and process one incoming message.
> > + *
> > + * For replies, find matching outgoing request and wake any waiters.
> > + * For requests, queue in incoming list and run request BH.
> > + */
> > +static int vfio_user_recv_one(VFIOProxy *proxy)
> > +{
> > +VFIOUserMsg
> -Original Message-
> From: Qemu-devel bounces+thanos.makatos=nutanix@nongnu.org> On Behalf Of John
> Johnson
> Sent: 12 January 2022 00:44
> To: qemu-devel@nongnu.org
> Subject: [RFC v4 08/21] vfio-user: define socket receive functions
>
> Add infra
l@nongnu.org
>> Subject: RE: [RFC v4 08/21] vfio-user: define socket receive functions
>>
>>
>>
>>> -Original Message-
>>> From: Qemu-devel >> bounces+thanos.makatos=nutanix@nongnu.org> On Behalf Of John
>>> Johnson
>>>
> -Original Message-
> From: Qemu-devel bounces+thanos.makatos=nutanix@nongnu.org> On Behalf Of Thanos
> Makatos
> Sent: 03 February 2022 21:54
> To: John Johnson ; qemu-devel@nongnu.org
> Subject: RE: [RFC v4 08/21] vfio-user: define soc
> -Original Message-
> From: Qemu-devel bounces+thanos.makatos=nutanix@nongnu.org> On Behalf Of John
> Johnson
> Sent: 12 January 2022 00:44
> To: qemu-devel@nongnu.org
> Subject: [RFC v4 08/21] vfio-user: define socket receive functions
>
> Add infra
Add infrastructure needed to receive incoming messages
Signed-off-by: John G Johnson
Signed-off-by: Elena Ufimtseva
Signed-off-by: Jagannathan Raman
---
hw/vfio/user-protocol.h | 54
hw/vfio/user.h | 6 +
hw/vfio/pci.c | 6 +
hw/vfio/user.c | 327
