All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/6] arm64/hyperv: Support Virtual Trust Level boot
Date: Fri, 10 May 2024 09:04:59 -0700	[thread overview]
Message-ID: <20240510160602.1311352-1-romank@linux.microsoft.com> (raw)

From: Roman Kisel <romank@linux.microsoft.com>

This set of patches enables the Hyper-V code to boot on ARM64
inside a Virtual Trust Level. These levels are a part of the
Virtual Secure Mode documented in the Top-Level Functional
Specification available at
https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/vsm

Roman Kisel (6):
  arm64/hyperv: Support DeviceTree
  drivers/hv: Enable VTL mode for arm64
  arm64/hyperv: Boot in a Virtual Trust Level
  drivers/hv: arch-neutral implementation of get_vtl()
  drivers/hv/vmbus: Get the irq number from DeviceTree
  drivers/pci/hyperv/arm64: vPCI MSI IRQ domain from DT

 arch/arm64/hyperv/Makefile          |  1 +
 arch/arm64/hyperv/hv_vtl.c          | 19 +++++++++++++
 arch/arm64/hyperv/mshyperv.c        | 40 +++++++++++++++++++++++----
 arch/arm64/include/asm/mshyperv.h   |  8 ++++++
 arch/x86/hyperv/hv_init.c           | 34 -----------------------
 arch/x86/hyperv/hv_vtl.c            |  2 +-
 arch/x86/include/asm/hyperv-tlfs.h  |  7 -----
 drivers/hv/Kconfig                  |  6 ++--
 drivers/hv/hv_common.c              | 43 +++++++++++++++++++++++++++++
 drivers/hv/vmbus_drv.c              | 37 +++++++++++++++++++++++++
 drivers/pci/controller/pci-hyperv.c | 13 +++++++--
 include/asm-generic/hyperv-tlfs.h   |  7 +++++
 include/asm-generic/mshyperv.h      |  6 ++++
 include/linux/acpi.h                | 10 +++++++
 14 files changed, 180 insertions(+), 53 deletions(-)
 create mode 100644 arch/arm64/hyperv/hv_vtl.c

-- 
2.45.0


             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 romank [this message]
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 ` [PATCH 2/6] drivers/hv: Enable VTL mode for arm64 romank
2024-05-12  2:54   ` 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-1-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.