[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [RFC v4 08/21] vfio-user: define socket receive functions
|
From: |
Thanos Makatos |
|
Subject: |
RE: [RFC v4 08/21] vfio-user: define socket receive functions |
|
Date: |
Wed, 16 Feb 2022 09:31:00 +0000 |
> -----Original Message-----
> From: John Johnson <john.g.johnson@oracle.com>
> Sent: 16 February 2022 02:10
> To: Thanos Makatos <thanos.makatos@nutanix.com>
> Cc: qemu-devel@nongnu.org
> Subject: Re: [RFC v4 08/21] vfio-user: define socket receive functions
>
>
>
> > On Feb 15, 2022, at 6:50 AM, Thanos Makatos
> <thanos.makatos@nutanix.com> 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 debug rfe. Maybe I’ll add one set for the normal path that
> prints an abbreviated header, and another set for the error case that prints
> the whole header. Would that work?
Yes that would be great.