On 13.11.2019 14:22, Andrew Cooper wrote: > I am not convinced the behaviour is worth changing, and I don't have > time for this scope creep.
There's no scope creep here at all. All I'm asking for is that you don't blindly OR in EFER_NX into trampoline_efer, but rather check that it will be possible to successfully set it after the MISC_ENABLE write (by reading back the value, or by reading CPUID[0x80000001].NX again). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
