On Sat, 12 Nov 2022 17:43:22 +0800, Gavin Shan wrote:
> In mark_page_dirty_in_slot(), we bail out when no running vcpu exists
> and a running vcpu context is strictly required by architecture. It may
> cause backwards compatible issue. Currently, saving vgic/its tables is
> the only known case where no running vcpu context is expected. We may
> have other unknown cases where no running vcpu context exists and it's
> reported by the warning message and we bail out without pushing the
> dirty information to the backup bitmap. For this, the application is
> going to enable the backup bitmap for the unknown cases. However, the
> dirty information can't be pushed to the backup bitmap even though the
> backup bitmap is enabled for those unknown cases in the application,
> until the unknown cases are added to the allowed list of non-running
> vcpu context with extra code changes to the host kernel.
>
> [...]
Applied to next, thanks!
[1/1] KVM: Push dirty information unconditionally to backup bitmap
commit c57351a75d013c30e4a726aef1ad441676a99da4
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
