From: Wei Liu <wei.liu@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Saurabh Sengar <ssengar@linux.microsoft.com>,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
mikelley@microsoft.com, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH] x86/hyperv: add noop functions to x86_init mpparse functions
Date: Fri, 2 Jun 2023 16:17:59 +0000 [thread overview]
Message-ID: <ZHoWN1TYicOSGsd3@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <442441b3-803e-0c1f-ff1b-5a49ecc2e423@intel.com>
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
I wished it could be more detailed.
With the proper configuration, VTL2 can see memory from VTL0, but not
the other way around.
Saurabh can probably give you more information for this particular setup.
Thanks,
Wei.
>
> $ grep -r VTL[02] Documentation/
> $
>
> Either way, this is way better than the #ifdefs. But the changelog is
> kinda just gibberish to me.
next prev parent reply other threads:[~2023-06-02 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 12:41 [PATCH] x86/hyperv: add noop functions to x86_init mpparse functions Saurabh Sengar
2023-06-02 15:33 ` Dave Hansen
2023-06-02 16:17 ` Wei Liu [this message]
2023-06-02 16:21 ` Dave Hansen
2023-06-02 16:22 ` Wei Liu
2023-06-02 16:27 ` [EXTERNAL] " Saurabh Singh Sengar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZHoWN1TYicOSGsd3@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox