Message ID | 20220721164331.3328625-1-eperezma@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | Control VQ is the way net devices use to send changes to the device state, like | expand |
On Thu, Jul 21, 2022 at 6:53 PM Eugenio Pérez <eperezma@redhat.com> wrote: > > > QEMU needs to intercept this queue so it can track these changes and is able to > migrate the device. It can do it from 1576dbb5bbc4 ("vdpa: Add x-svq to > NetdevVhostVDPAOptions"). However, to enable x-svq implies to shadow all VirtIO > device's virtqueues, which will damage performance. > > This series adds address space isolation, so the device and the guest > communicate directly with them (passthrough) and CVQ communication is split in > two: The guest communicates with QEMU and QEMU forwards the commands to the > device. > > This series is based on [1], although each one of them adds a feature on > isolation and could be merged individually once conflicts are solved. > > Comments are welcome. Thanks! > > [1] https://lists.nongnu.org/archive/html/qemu-devel/2022-07/msg03101.html > The title of this series should be "vDPA net ASID support" or something like that, I forgot that first line by mistake. Should I resend it or can it stay like that? Thanks!