From: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
To: "Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
Dexuan Cui <decui@microsoft.com>, "arnd@arndb.de" <arnd@arndb.de>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v3 5/5] x86/Kconfig: Add HYPERV_VTL_MODE
Date: Sun, 26 Mar 2023 09:47:00 -0700 [thread overview]
Message-ID: <20230326164700.GA10074@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <BYAPR21MB16885C786D5DC8381C21868AD78A9@BYAPR21MB1688.namprd21.prod.outlook.com>
On Sun, Mar 26, 2023 at 03:16:15PM +0000, Michael Kelley (LINUX) wrote:
> From: Saurabh Sengar <ssengar@linux.microsoft.com> Sent: Monday, March 20, 2023 3:04 AM
> >
> > Add HYPERV_VTL_MODE Kconfig flag for VTL mode.
> >
> > Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
> > ---
> > arch/x86/Kconfig | 24 ++++++++++++++++++++++++
> > arch/x86/hyperv/Makefile | 1 +
> > 2 files changed, 25 insertions(+)
> >
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 453f462f6c9c..c3faaaea1e31 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -782,6 +782,30 @@ menuconfig HYPERVISOR_GUEST
> >
> > if HYPERVISOR_GUEST
> >
> > +config HYPERV_VTL_MODE
> > + bool "Enable Linux to boot in VTL context"
> > + depends on X86_64 && HYPERV
> > + default n
> > + help
> > + Virtual Secure Mode (VSM) is a set of hypervisor capabilities and
> > + enlightenments offered to host and guest partitions which enables
> > + the creation and management of new security boundaries within
> > + operating system software.
> > +
> > + VSM achieves and maintains isolation through Virtual Trust Levels
> > + (VTLs). Virtual Trust Levels are hierarchical, with higher levels
> > + being more privileged than lower levels. VTL0 is the least privileged
> > + level, and currently only other level supported is VTL2.
> > +
> > + Select this option to build a Linux kernel to run at a VTL other than
> > + the normal VTL0, which currently is only VTL2. This option
> > + initializes the x86 platform for VTL2, and adds the ability to boot
> > + secondary CPUs directly into 64-bit context as required for VTLs other
> > + than 0. A kernel built with this option must run at VTL2, and will
> > + not run as a normal guest.
> > +
> > + If unsure, say N
> > +
>
> Is there a reason for putting this in arch/x86/Kconfig instead of in
> drivers/hv/Kconfig under the "Microsoft Hyper-V guest support"
> menu with the other Hyper-V settings? It seems like grouping
> this with the other Hyper-V settings would make it easier to find,
> unless there's some reason that doesn't work.
As all the code dependent on this flag is in arch/x86/hyperv, and all
other kernel flags used in arch/x86/hyperv/Makefile are define in
arch/x86/Kconfig, arch/x86/Kconfig was my default choice.
But your suggestion makes perfect sense, I will move it to
drivers/hv/Kconfig
Regards,
Saurabh
>
> Michael
>
> > config PARAVIRT
> > bool "Enable paravirtualization code"
> > depends on HAVE_STATIC_CALL
> > diff --git a/arch/x86/hyperv/Makefile b/arch/x86/hyperv/Makefile
> > index 5d2de10809ae..3a1548054b48 100644
> > --- a/arch/x86/hyperv/Makefile
> > +++ b/arch/x86/hyperv/Makefile
> > @@ -1,6 +1,7 @@
> > # SPDX-License-Identifier: GPL-2.0-only
> > obj-y := hv_init.o mmu.o nested.o irqdomain.o ivm.o
> > obj-$(CONFIG_X86_64) += hv_apic.o hv_proc.o
> > +obj-$(CONFIG_HYPERV_VTL_MODE) += hv_vtl.o
> >
> > ifdef CONFIG_X86_64
> > obj-$(CONFIG_PARAVIRT_SPINLOCKS) += hv_spinlock.o
> > --
> > 2.34.1
prev parent reply other threads:[~2023-03-26 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:03 [PATCH v3 0/5] Hyper-V VTL support Saurabh Sengar
2023-03-20 10:03 ` [PATCH v3 1/5] x86/init: Make get/set_rtc_noop() public Saurabh Sengar
2023-03-26 15:03 ` Michael Kelley (LINUX)
2023-03-27 4:47 ` Saurabh Singh Sengar
2023-03-20 10:03 ` [PATCH v3 2/5] x86/hyperv: Add VTL specific structs and hypercalls Saurabh Sengar
2023-03-26 15:05 ` Michael Kelley (LINUX)
2023-03-20 10:03 ` [PATCH v3 3/5] x86/hyperv: Make hv_get_nmi_reason public Saurabh Sengar
2023-03-26 15:06 ` Michael Kelley (LINUX)
2023-03-20 10:03 ` [PATCH v3 4/5] x86/hyperv: VTL support for Hyper-V Saurabh Sengar
2023-03-20 18:16 ` Michael Kelley (LINUX)
2023-03-21 11:27 ` Saurabh Singh Sengar
2023-03-20 10:03 ` [PATCH v3 5/5] x86/Kconfig: Add HYPERV_VTL_MODE Saurabh Sengar
2023-03-26 15:16 ` Michael Kelley (LINUX)
2023-03-26 16:47 ` Saurabh Singh Sengar [this message]
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=20230326164700.GA10074@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=ssengar@linux.microsoft.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).