From: Marc Zyngier <firstname.lastname@example.org>
To: Michael Kelley <email@example.com>
Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org, email@example.com,
Subject: Re: [PATCH v11 0/5] Enable Linux guests on Hyper-V on ARM64
Date: Mon, 02 Aug 2021 17:01:02 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Tue, 20 Jul 2021 15:56:58 +0100,
Michael Kelley <email@example.com> wrote:
> This series enables Linux guests running on Hyper-V on ARM64
> hardware. New ARM64-specific code in arch/arm64/hyperv initializes
> Hyper-V and its hypercall mechanism. Existing architecture
> independent drivers for Hyper-V's VMbus and synthetic devices just
> work when built for ARM64. Hyper-V code is built and included in
> the image and modules only if CONFIG_HYPERV is enabled.
> The five patches are organized as follows:
> 1) Add definitions and functions for making Hyper-V hypercalls
> and getting/setting virtual processor registers provided by
> 2) Add the function needed by the arch independent VMbus driver
> for reporting a panic to Hyper-V.
> 3) Add Hyper-V initialization code and utility functions that
> report Hyper-v status.
> 4) Export screen_info so it may be used by the Hyper-V frame buffer
> driver built as a module. It is already exported for x86,
> powerpc, and alpha architectures.
> 5) Make CONFIG_HYPERV selectable on ARM64 in addition to x86/x64.
> Hyper-V on ARM64 runs with a 4 Kbyte page size, but allows guests
> with 4K/16K/64K page size. Linux guests with this patch series
> work with all three supported ARM64 page sizes.
> The Hyper-V vPCI driver at drivers/pci/host/pci-hyperv.c has
> x86/x64-specific code and is not being built for ARM64. Enabling
> Hyper-V vPCI devices on ARM64 is in progress via a separate set
> of patches.
> This patch set is based on the linux-next20210720 code tree.
> Changes in v11:
> * Drop the previous Patch 1 as the fixes have already been
> separately accepted upstream.
> * Drop the previous Patch 3 for enabling Hyper-V enlightened
> clocks/timers. Hyper-V is now offering the full ARM64
> architectural Generic Timer in guest VMs, so the existing
> arch_arch_timer.c driver just works. [Mark Rutland, Marc
Thanks for doing this. Assuming you fix the issue I mentioned in my
reply to patch #3. FWIW:
Acked-by: Marc Zyngier <firstname.lastname@example.org>
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-08-02 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 14:56 [PATCH v11 0/5] Enable Linux guests on Hyper-V on ARM64 Michael Kelley
2021-07-20 14:56 ` [PATCH v11 1/5] arm64: hyperv: Add Hyper-V hypercall and register access utilities Michael Kelley
2021-07-20 14:57 ` [PATCH v11 2/5] arm64: hyperv: Add panic handler Michael Kelley
2021-07-21 14:54 ` Boqun Feng
2021-07-27 17:08 ` Sunil Muthuswamy
2021-07-20 14:57 ` [PATCH v11 3/5] arm64: hyperv: Initialize hypervisor on boot Michael Kelley
2021-07-21 14:55 ` Boqun Feng
2021-07-27 17:05 ` Sunil Muthuswamy
2021-08-02 15:55 ` Marc Zyngier
2021-08-02 16:26 ` Mark Rutland
2021-08-02 17:13 ` Michael Kelley
2021-07-20 14:57 ` [PATCH v11 4/5] arm64: efi: Export screen_info Michael Kelley
2021-07-20 14:57 ` [PATCH v11 5/5] Drivers: hv: Enable Hyper-V code to be built on ARM64 Michael Kelley
2021-07-21 14:52 ` Boqun Feng
2021-08-02 15:15 ` [PATCH v11 0/5] Enable Linux guests on Hyper-V " Michael Kelley
2021-08-02 16:01 ` Marc Zyngier [this message]
2021-08-02 16:28 ` Mark Rutland
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).