From: romank@linux.microsoft.com
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, linux-hyperv@vger.kernel.org,
rafael@kernel.org, lenb@kernel.org, linux-acpi@vger.kernel.org
Cc: ssengar@microsoft.com, sunilmut@microsoft.com
Subject: [PATCH 2/6] drivers/hv: Enable VTL mode for arm64
Date: Fri, 10 May 2024 09:05:01 -0700 [thread overview]
Message-ID: <20240510160602.1311352-3-romank@linux.microsoft.com> (raw)
In-Reply-To: <20240510160602.1311352-1-romank@linux.microsoft.com>
From: Roman Kisel <romank@linux.microsoft.com>
This change removes dependency on ACPI when buidling the hv drivers to
allow Virtual Trust Level boot with DeviceTree.
Signed-off-by: Roman Kisel <romank@linux.microsoft.com>
---
drivers/hv/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/hv/Kconfig b/drivers/hv/Kconfig
index 862c47b191af..a5cd1365e248 100644
--- a/drivers/hv/Kconfig
+++ b/drivers/hv/Kconfig
@@ -5,7 +5,7 @@ menu "Microsoft Hyper-V guest support"
config HYPERV
tristate "Microsoft Hyper-V client drivers"
depends on (X86 && X86_LOCAL_APIC && HYPERVISOR_GUEST) \
- || (ACPI && ARM64 && !CPU_BIG_ENDIAN)
+ || (ARM64 && !CPU_BIG_ENDIAN)
select PARAVIRT
select X86_HV_CALLBACK_VECTOR if X86
select OF_EARLY_FLATTREE if OF
@@ -15,7 +15,7 @@ config HYPERV
config HYPERV_VTL_MODE
bool "Enable Linux to boot in VTL context"
- depends on X86_64 && HYPERV
+ depends on HYPERV
depends on SMP
default n
help
@@ -31,7 +31,7 @@ config HYPERV_VTL_MODE
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
+ initializes the kernel to run in 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.
--
2.45.0
next prev parent reply other threads:[~2024-05-10 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 16:04 [PATCH 0/6] arm64/hyperv: Support Virtual Trust Level boot romank
2024-05-10 16:05 ` [PATCH 1/6] arm64/hyperv: Support DeviceTree romank
2024-05-10 17:04 ` Easwar Hariharan
2024-05-10 17:42 ` Roman Kisel
2024-05-14 22:46 ` Easwar Hariharan
2024-05-14 23:17 ` Roman Kisel
2024-05-15 0:00 ` Easwar Hariharan
2024-05-20 17:08 ` Roman Kisel
2024-05-10 16:05 ` romank [this message]
2024-05-12 2:54 ` [PATCH 2/6] drivers/hv: Enable VTL mode for arm64 kernel test robot
2024-05-15 7:43 ` Wei Liu
2024-05-20 17:00 ` Roman Kisel
2024-05-10 16:05 ` [PATCH 3/6] arm64/hyperv: Boot in a Virtual Trust Level romank
2024-05-10 16:05 ` [PATCH 4/6] drivers/hv: arch-neutral implementation of get_vtl() romank
2024-05-10 16:05 ` [PATCH 5/6] drivers/hv/vmbus: Get the irq number from DeviceTree romank
2024-05-10 16:05 ` [PATCH 6/6] drivers/pci/hyperv/arm64: vPCI MSI IRQ domain from DT romank
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=20240510160602.1311352-3-romank@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ssengar@microsoft.com \
--cc=sunilmut@microsoft.com \
--cc=wei.liu@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).