[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 02 Feb 2022 12:34:31 +0100
From: Cornelia Huck <cohuck@...hat.com>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Yishai Hadas <yishaih@...dia.com>, alex.williamson@...hat.com,
bhelgaas@...gle.com, saeedm@...dia.com, linux-pci@...r.kernel.org,
kvm@...r.kernel.org, netdev@...r.kernel.org, kuba@...nel.org,
leonro@...dia.com, kwankhede@...dia.com, mgurtovoy@...dia.com,
maorg@...dia.com
Subject: Re: [PATCH V6 mlx5-next 10/15] vfio: Remove migration protocol v1
On Tue, Feb 01 2022, Jason Gunthorpe <jgg@...dia.com> wrote:
> On Tue, Feb 01, 2022 at 03:19:18PM +0100, Cornelia Huck wrote:
>> (- also continue to get the documentation into good shape)
>
> Which items do you see here?
Well, it still needs to be updated, no?
>
>> - have an RFC for QEMU that contains a provisional update of the
>> relevant vfio headers so that we can discuss the QEMU side (and maybe
>> shoot down any potential problems in the uapi before they are merged
>> in the kernel)
>
> This qemu patch is linked in the cover letter.
The QEMU changes need to be discussed on qemu-devel, a link to a git
tree with work in progress only goes so far.
(From my quick look there, this needs to have any headers changes split
out into a separate patch. The changes in migration.c are hard to
review; is there any chance to split the error path cleanups from the
interface changes?)
Powered by blists - more mailing lists