The remainingI think I am coming to quite like that 'remaining option' as long as we
option would be just "do not mark the page as dirty if the ring buffer
is active". This is feasible because userspace itself has passed the
shared info gfn; but again, it's ugly...
rephrase it as follows:
KVM does not mark the shared_info page as dirty, and userspace is
expected to*assume* that it is dirty at all times. It's used for
delivering event channel interrupts and the overhead of marking it
dirty each time is just pointless.