> On Mar 9, 2022, at 2:34 PM, Alex Williamson <alex.william...@redhat.com> > wrote: > > On Tue, 11 Jan 2022 16:43:37 -0800 > John Johnson <john.g.john...@oracle.com> wrote: >> >> + >> +VFIO region type cap header >> +""""""""""""""""""""""""""" >> + >> ++------------------+---------------------------+ >> +| Name | Value | >> ++==================+===========================+ >> +| id | VFIO_REGION_INFO_CAP_TYPE | >> ++------------------+---------------------------+ >> +| version | 0x1 | >> ++------------------+---------------------------+ >> +| next | <next> | >> ++------------------+---------------------------+ >> +| region info type | VFIO region info type | >> ++------------------+---------------------------+ >> + >> +This capability is defined when a region is specific to the device. >> + >> +VFIO region info type cap >> +""""""""""""""""""""""""" >> + >> +The VFIO region info type is defined in ``<linux/vfio.h>`` >> +(``struct vfio_region_info_cap_type``). >> + >> ++---------+--------+------+ >> +| Name | Offset | Size | >> ++=========+========+======+ >> +| type | 0 | 4 | >> ++---------+--------+------+ >> +| subtype | 4 | 4 | >> ++---------+--------+------+ >> + >> +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 interface. I > hope there are plans for vfio-user to adopt the new interface that's > currently available in linux-next and intended for v5.18. >
I re-issued the series without v1 migration support, but I haven’t seen any additional feedback. What do you think the next step should be? Wait for v2 to be pulled and merge it? Something else? Thank you. JJ no migration URL: https://lists.gnu.org/archive/html/qemu-devel/2022-05/msg01105.html