On 6/18/2022 12:51 AM, Alex Williamson wrote:
External email: Use caution opening links or attachments
On Mon, 13 Jun 2022 14:21:26 +0300
Avihai Horon wrote:
On 6/8/2022 12:32 AM, Alex Williamson wrote:
External email: Use caution opening links or attachments
On Tue, 7 Jun 2022
On Fri, Jun 17, 2022 at 03:51:29PM -0600, Alex Williamson wrote:
> It's ok by me if QEMU vfio is the one that marks all mapped pages dirty
> if the host interface provides no way to do so. Would we toggle that
> based on whether the device has bus-master enabled?
I don't think so, that is a
On Mon, 13 Jun 2022 14:21:26 +0300
Avihai Horon wrote:
> On 6/8/2022 12:32 AM, Alex Williamson wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On Tue, 7 Jun 2022 20:44:23 +0300
> > Avihai Horon wrote:
> >
> >> On 5/30/2022 8:07 PM, Avihai Horon wrote:
> >>>
On 6/8/2022 12:32 AM, Alex Williamson wrote:
External email: Use caution opening links or attachments
On Tue, 7 Jun 2022 20:44:23 +0300
Avihai Horon wrote:
On 5/30/2022 8:07 PM, Avihai Horon wrote:
Hello,
Following VFIO migration protocol v2 acceptance in kernel, this series
implements
On Tue, 7 Jun 2022 20:44:23 +0300
Avihai Horon wrote:
> On 5/30/2022 8:07 PM, Avihai Horon wrote:
> > Hello,
> >
> > Following VFIO migration protocol v2 acceptance in kernel, this series
> > implements VFIO migration according to the new v2 protocol and replaces
> > the now deprecated v1
On 5/30/2022 8:07 PM, Avihai Horon wrote:
Hello,
Following VFIO migration protocol v2 acceptance in kernel, this series
implements VFIO migration according to the new v2 protocol and replaces
the now deprecated v1 implementation.
The main differences between v1 and v2 migration protocols
Hello,
Following VFIO migration protocol v2 acceptance in kernel, this series
implements VFIO migration according to the new v2 protocol and replaces
the now deprecated v1 implementation.
The main differences between v1 and v2 migration protocols are:
1. VFIO device state is represented as a
