On 6/2/23 09:17, Wei Liu wrote: > On Fri, Jun 02, 2023 at 08:33:13AM -0700, Dave Hansen wrote: >> On 6/2/23 05:41, Saurabh Sengar wrote: >>> In !ACPI system, there is no way to disable CONFIG_X86_MPPARSE. >>> When CONFIG_X86_MPPARSE is enabled for VTL2, the kernel will >>> scan low memory looking for MP tables. Don't allow this, because >>> low memory is controlled by VTL0 and may contain actual valid >>> tables for VTL0, which can confuse the VTL2 kernel. >> Do you folks have a writeup of this VTL* setup anywhere? I'm struggling >> to grasp why VTL0 and VTL2 share the same address space and why they >> would get confused by each other's data structures. > Dave, here is some public information about Virtual Trust Level. > > https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/vsm#virtual-trust-level-vtl Yeah, I can google too. ;) Seriously, though. I don't need an architecture document. This is like me asking how NMIs work in Linux and someone pointing me to the SDM describing the hardware architecture. I need to know about the Linux implementation of these VTL's, not the overall VTL architecture.
