> On Mar 9, 2022, at 2:34 PM, Alex Williamson
> wrote:
>
> On Tue, 11 Jan 2022 16:43:37 -0800
> John Johnson wrote:
>>
>> +
>> +VFIO region type cap header
>> +"""
>> +
>> ++--+---+
>> +| Name | Value
Cc: qemu-devel@nongnu.org
> > Subject: Re: [RFC v4 01/21] vfio-user: introduce vfio-user protocol
> > specification
> >
> > On Tue, 11 Jan 2022 16:43:37 -0800
> > John Johnson wrote:
> > > +VFIO region info cap sparse mmap
> > > +"""&q
> -Original Message-
> From: Qemu-devel bounces+thanos.makatos=nutanix@nongnu.org> On Behalf Of Alex
> Williamson
> Sent: 09 March 2022 22:35
> To: John Johnson
> Cc: qemu-devel@nongnu.org
> Subject: Re: [RFC v4 01/21] vfio-user: introduce vfio-user p
> On Mar 9, 2022, at 2:34 PM, Alex Williamson
> wrote:
>
>>
>> +
>> +VFIO region info type cap
>> +"
>> +
>> +The VFIO region info type is defined in
>> +(``struct vfio_region_info_cap_type``).
>> +
>> ++-++--+
>> +| Name| Offset | Size |
On Wed, Mar 09, 2022 at 03:34:53PM -0700, Alex Williamson wrote:
> > +The only device-specific region type and subtype supported by vfio-user is
> > +``VFIO_REGION_TYPE_MIGRATION`` (3) and ``VFIO_REGION_SUBTYPE_MIGRATION``
> > (1).
>
> These should be considered deprecated from the kernel
On Tue, 11 Jan 2022 16:43:37 -0800
John Johnson wrote:
> +VFIO region info cap sparse mmap
> +
> +
> ++--++--+
> +| Name | Offset | Size |
> ++==++==+
> +| nr_areas | 0 | 4|
> ++--++--+
> +|
> -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 01/21] vfio-user: introduce vfio-user protocol specification
>
From: Thanos Makatos
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
