On Wed, Aug 04, 2021 at 04:39:02PM +0000, Michael Kelley wrote: > From: Catalin Marinas <catalin.marinas@xxxxxxx> Sent: Wednesday, August 4, 2021 9:26 AM > > > > On Wed, Aug 04, 2021 at 08:52:34AM -0700, Michael Kelley 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. > > [...] > > > 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. > > > > Is it possible to rebase this on top of -rc3? Are there any > > dependencies or do you plan to upstream this via a different tree? > > There are dependencies on changes in the hyperv-next tree > (https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/) > which is why you are getting the build errors. The changes > common-ized some code between the x86 side and previous > versions of this patch set (and fixed the #include nmi.h problem). > So the code would most naturally go upstream through that tree. In that case, for this series: Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx> I don't think there'd be conflicts with the arm64 changes but we can spot them early in -next. -- Catalin
