On Tue, Aug 29, 2023, Michael Roth wrote: > So we need to be able to deal with that even for 'well-behaved' guests. > With RMP-init-during-mapping-time approach I had some checks that avoided > creating the 2MB RMP entry in this mixed case which is why I didn't need > handling for this previously. But it's just one extra #NPF(RMP) and can > be handled cleanly since it can be distinguished from spurious cases. Just to make sure you're not waiting on me for something, the TL;DR is that my suggestion is viable and not too horrific?
