>-Original Message-
>From: Prasad Pandit
>Subject: Re: [PATCH v1 6/6] intel_iommu: Block migration if cap is updated
>
>On Mon, 4 Mar 2024 at 13:41, Duan, Zhenzhong
> wrote:
>> This is to deal with a special case when cold plugged vfio device is
>unplugged
&g
On Mon, 4 Mar 2024 at 13:41, Duan, Zhenzhong wrote:
> This is to deal with a special case when cold plugged vfio device is unplugged
> at runtime, then migration triggers.
>
> When qemu on source side starts with cold plugged vfio device, vIOMMU
qemu -> QEMU
> capability/extended capability
>-Original Message-
>From: Prasad Pandit
>Subject: Re: [PATCH v1 6/6] intel_iommu: Block migration if cap is updated
>
>On Wed, 28 Feb 2024 at 15:17, Zhenzhong Duan
> wrote:
>> When there is VFIO device and vIOMMU cap/ecap is updated based on
>host
>
>
On Wed, 28 Feb 2024 at 15:17, Zhenzhong Duan wrote:
> When there is VFIO device and vIOMMU cap/ecap is updated based on host
* cap/ecap -> capability/extended capability registers are updated ...
> IOMMU cap/ecap, migration should be blocked.
* It'll help to mention why migration should be
