On 1/19/22 09:14, David Woodhouse wrote:
Or do we have explicit other requirement that needs to dirty guest pages
without vcpu context at all?
Delivering interrupts may want to do so. That's the one we hit for
S390, and I only avoided it for Xen event channel delivery on x86 by
declaring that the Xen shared info page is exempt from dirty tracking
and should*always* be considered dirty.
We also have one that I just found out about in
kvm_hv_invalidate_tsc_page, called from KVM_SET_CLOCK. :/
So either we have another special case to document for the dirty ring
buffer (and retroactively so, even), or we're in bad need for a solution.
Paolo
