hangpeng@intel.com;
> dgilb...@redhat.com
> Subject: Re: [PATCH v5] introduce vfio-user protocol specification
>
> On Thu, Nov 05, 2020 at 05:50:27PM -0800, John G Johnson wrote:
>
> > The idea behind the version IDs is to identify incompatible protocol
> > cha
> > > * *Error* in a reply message indicates the command being
> acknowledged
> > had
> > > an error. In this case, the *Error* field will be valid.
> > >
> > > * *Error* in a reply message is a UNIX errno value. It is reserved in a
> > command message.
> >
> > I'm not quite following why we
On Thu, Nov 05, 2020 at 05:50:27PM -0800, John G Johnson wrote:
> The idea behind the version IDs is to identify incompatible protocol
> changes as major versions, and compatible changes as minor versions. What
> would be the purpose of the third version type?
Well, like any patch
.com; Marc-André Lureau
>> ; ism...@linux.com;
>> alex.william...@redhat.com; Stefan Hajnoczi ;
>> Felipe Franciosi ; xiuchun...@intel.com;
>> tomassetti.and...@gmail.com; changpeng....@intel.com; Raphael Norwitz
>> ; kanth.ghatr...@oracle.com
>> Subject: Re: [PA
iosi ; xiuchun...@intel.com;
> tomassetti.and...@gmail.com; changpeng@intel.com; Raphael Norwitz
> ; kanth.ghatr...@oracle.com
> Subject: Re: [PATCH v5] introduce vfio-user protocol specification
>
> On
On Mon, Nov 02, 2020 at 11:29:23AM +, Thanos Makatos wrote:
> > +==++=
> > ==+
> > > | version | object | ``{"major": , "minor": }``
> > > |
> > > | ||
u
> ; tina.zh...@intel.com;
> changpeng@intel.com
> Subject: Re: [PATCH v5] introduce vfio-user protocol specification
>
> On Wed, Oct 28, 2020 at 04:41:31PM +, Thanos Makatos wrote:
>
> > FYI here's v5 of the vfio-user protocol, my --cc in git send-email got
> > messed
On Wed, Oct 28, 2020 at 04:41:31PM +, Thanos Makatos wrote:
> FYI here's v5 of the vfio-user protocol, my --cc in git send-email got messed
> up somehow
Hi Thanos, this looks great, I just had some minor questions below.
> Command Concurrency
> ---
> A client may pipeline
t; Subject: [PATCH v5] introduce vfio-user protocol specification
>
> This patch introduces the vfio-user protocol specification (formerly
> known as VFIO-over-socket), which is designed to allow devices to be
> emulated outside QEMU, in a separate process. vfio-user reuses the
This patch introduces the vfio-user protocol specification (formerly
known as VFIO-over-socket), which is designed to allow devices to be
emulated outside QEMU, in a separate process. vfio-user reuses the
existing VFIO defines, structs and concepts.
It has been earlier discussed as an RFC in:
10 matches
Mail list logo
