* Alex Williamson (alex.william...@redhat.com) wrote:
> On Thu, 25 Jun 2020 20:31:12 +0530
> Kirti Wankhede wrote:
>
> > On 6/25/2020 12:26 AM, Alex Williamson wrote:
> > > On Sun, 21 Jun 2020 01:51:24 +0530
> > > Kirti Wankhede wrote:
> > >
> > >> With vIOMMU, IO virtual address range can ge
On Thu, 25 Jun 2020 20:31:12 +0530
Kirti Wankhede wrote:
> On 6/25/2020 12:26 AM, Alex Williamson wrote:
> > On Sun, 21 Jun 2020 01:51:24 +0530
> > Kirti Wankhede wrote:
> >
> >> With vIOMMU, IO virtual address range can get unmapped while in pre-copy
> >> phase of migration. In that case, un
On 6/25/2020 12:26 AM, Alex Williamson wrote:
On Sun, 21 Jun 2020 01:51:24 +0530
Kirti Wankhede wrote:
With vIOMMU, IO virtual address range can get unmapped while in pre-copy
phase of migration. In that case, unmap ioctl should return pages pinned
in that range and QEMU should find its cor
On Sun, 21 Jun 2020 01:51:24 +0530
Kirti Wankhede wrote:
> With vIOMMU, IO virtual address range can get unmapped while in pre-copy
> phase of migration. In that case, unmap ioctl should return pages pinned
> in that range and QEMU should find its correcponding guest physical
> addresses and repo
On Sun, 21 Jun 2020 01:51:24 +0530
Kirti Wankhede wrote:
> With vIOMMU, IO virtual address range can get unmapped while in pre-copy
> phase of migration. In that case, unmap ioctl should return pages pinned
> in that range and QEMU should find its correcponding guest physical
> addresses and repo
With vIOMMU, IO virtual address range can get unmapped while in pre-copy
phase of migration. In that case, unmap ioctl should return pages pinned
in that range and QEMU should find its correcponding guest physical
addresses and report those dirty.
Suggested-by: Alex Williamson
Signed-off-by: Kirt
