Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp955826imu; Thu, 22 Nov 2018 07:51:52 -0800 (PST) X-Google-Smtp-Source: AFSGD/UWUbx6JnV7qpd8s059dK1TT/n/nNFmsdojLsxA4rCvpoHfY+lsOfrE3CkqRt9lhzeG8fii X-Received: by 2002:a65:40c5:: with SMTP id u5mr10214762pgp.46.1542901912568; Thu, 22 Nov 2018 07:51:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542901912; cv=none; d=google.com; s=arc-20160816; b=gwOTxlZoGR34RSDOvbnH9lS/ynMJi/gGDNnk9+DzzFMQI0byFzERUhmV5BIakWXEq7 VQo5kC4MAkK2JZi1ECjkYutf8NoXE4Of0lCkUHTJFOewCwCku3c8WqPaF3L5JaanMBHI ODVIihynVPJ0s9Ks4EV3zH2JlOc8d6uIDhMA4VmDHpoirXxPepMGib+bk2lTaa2DP7Se IV5pzsGDQsV9PxyUKhl/+44aO6hxa5X6WAwgvIfDCq77WP41YK63yrJNG6a1vCJvTGMU QG4wTMODDlIcymVwkY14jqe473fqrLCNlkTJAArxI/kjJ6y8qIOGPuesmXblm+851ahT Gytg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:reply-to :mime-version:message-id:date:subject:cc:to:from; bh=pvkMvLc/Vsuotb/ogtT0lNdszj/dLtak2pujxQBb3Ng=; b=DXHQYHJ8Z1aWLrY61f470GVzvy/CSzLLurIEOnAJh2BL293hBhYMk7GOjYE06bbMh6 1s4gHEABe/Gd+A5PQPCGMwUBml+BpIC4cVuS0goLVXN5kKwPlzzKBq2+fyP9t97dvn/4 PA3X1dZuT7inJRoE/NefHJONNE9HnNmNsKCzIL6k+wl9P1N6tsGl7do9op0Dn4S03XuP p3aXVJ1XK+GKR8XlqrvoM1wg827/mrRAqHo+yXA0j9LwVTFFUtoF282hxKiUGf9gjvl/ PXGXWn0H1r3u/RM2zGfJoLYSRY7YJWUscg3O0QY0JLFkeKhR2kbwsepsRoJQL4NdefnD UPew== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t64si6050153pgd.202.2018.11.22.07.51.38; Thu, 22 Nov 2018 07:51:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391846AbeKVNrh (ORCPT + 99 others); Thu, 22 Nov 2018 08:47:37 -0500 Received: from a2nlsmtp01-05.prod.iad2.secureserver.net ([198.71.225.49]:33078 "EHLO a2nlsmtp01-05.prod.iad2.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732413AbeKVNrh (ORCPT ); Thu, 22 Nov 2018 08:47:37 -0500 Received: from linuxonhyperv2.linuxonhyperv.com ([107.180.71.197]) by : HOSTING RELAY : with ESMTP id PfMigqyEMse9VPfMigyvBh; Wed, 21 Nov 2018 20:09:16 -0700 x-originating-ip: 107.180.71.197 Received: from kys by linuxonhyperv2.linuxonhyperv.com with local (Exim 4.91) (envelope-from ) id 1gPfMi-0004FB-5J; Wed, 21 Nov 2018 20:09:16 -0700 From: kys@linuxonhyperv.com To: will.deacon@arm.com, catalin.marinas@armm.com, mark.rutland@arm.com, marc.zyngier@arm.com, linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com, sthemmin@microsoft.com, Michael.H.Kelley@microsoft.com, vkuznets@redhat.com Cc: "K. Y. Srinivasan" Subject: [PATCH 0/4] Hyper-V: Enable Linux guests on Hyper-V on ARM64 Date: Thu, 22 Nov 2018 03:09:14 +0000 Message-Id: <20181122030914.16274-1-kys@linuxonhyperv.com> X-Mailer: git-send-email 2.19.1 MIME-Version: 1.0 Reply-To: kys@microsoft.com Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfO4UCel2TN4PKno+wg36SaJV57cKu0LDwil6qRUUtef/Xrc6Yqd7kX9O0wJZN0YsEY9XZQDgkS4nwryBHsNwz6xnUsNtXfqaEiHDkSQV2e/tU2DoTkqB 5xPUZY6AIfiWs6kBzvuW4a/MQJu0sz5sLZZSnPispnVOeabZ181VPPeSEdnGApmoDetPSomci3piApl8g4PT1kJQZsRyri0/Xto3U6CteauxWrO3JbLVycrv BSBTS9yMRsbpUtl/kaJei7qfczLavU6qmjoYBtmJUWsIoO0iBddHvmUXOWnaFKCwwU1DmFJTGRIFTiP0yj3tXT7CEMW2gSIGV3jQzXifUn9qYqK0CoEbCbN2 +ZY48Mm3smnEbWx6JTZPWycbdCOU1XDjjzqJpkJuDQU8eXG4BCv3EFkK5i1x25CTsn6Jr38vxlp34ps5uuCbSH0kWMd0DqAM9H2OuEtT3Vc4Lt6ed6ZK/JwS bB3YIZn7eeZNHfyYKUtK2ZIxDmEVWWay5KnGlirjIkHYXtRuXC3/V2PDv7x+8dnMZrd36ZWr79pdQeSu3uY5AHdObEGjUhvJLCNT+UiIITIDyCXfigrULr/O GtZ5iomojHfGd//OVuMReuZGlIkb4fH4vwKfSior1KcyBF9U/yH/WM9X5rNyUVtLHnZ5lQBYETOO/1tGI54nOLtODeRBCtOZMqde3dZNt1fPqNzlQtD4e2mm 9ELboxxOqtA= Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "K. Y. Srinivasan" This series enables Linux guests running on Hyper-V on ARM64 hardware. New ARM64-specific code in arch/arm64/hyperv initializes Hyper-V, including its synthetic clocks and 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 four patches are organized as follows: 1) Add include files that define the Hyper-V interface as described in the Hyper-V Top Level Functional Spec (TLFS), plus additional definitions specific to Linux running on Hyper-V. 2) Add core Hyper-V support on ARM64, including hypercalls, synthetic clock initialization, and interrupt handlers. 3) Update the existing VMbus driver to generalize interrupt management across x86/x64 and ARM64. 4) Make CONFIG_HYPERV selectable on ARM64 in addition to x86/x64. Some areas of Linux guests on Hyper-V on ARM64 are a work- in-progress, primarily due to work still being done in Hyper-V: * Hyper-V on ARM64 currently runs with a 4 Kbyte page size, and only supports guests with a 4 Kbyte page size. Because Hyper-V uses shared pages to communicate between the guest and the hypervisor, there are open design decisions on the page size to use when the guest is using 16K/64K pages. Once those issues are resolved and Hyper-V fully supports 16K/64K guest pages, changes may be needed in the Linux drivers for Hyper-V synthetic devices. * Hyper-V on ARM64 does not currently support mapping PCI devices into the guest address space. The Hyper-V PCI driver at drivers/pci/host/pci-hyperv.c has x86/x64-specific code and is not being built for ARM64. In a few cases, terminology from the x86/x64 world has been carried over into the ARM64 code ("MSR", "TSC"). Hyper-V still uses the x86/x64 terminology and has not replaced it with something more generic, so the code uses the Hyper-V terminology. This will be fixed when Hyper-V updates the usage in the TLFS. Michael Kelley (4): arm64: hyperv: Add core Hyper-V include files arm64: hyperv: Add support for Hyper-V as a hypervisor Drivers: hv: vmbus: Add hooks for per-CPU IRQ Drivers: hv: Enable CONFIG_HYPERV on ARM64 MAINTAINERS | 4 + arch/arm64/Makefile | 1 + arch/arm64/hyperv/Makefile | 2 + arch/arm64/hyperv/hv_hvc.S | 54 ++++ arch/arm64/hyperv/hv_init.c | 441 +++++++++++++++++++++++++++ arch/arm64/hyperv/mshyperv.c | 178 +++++++++++ arch/arm64/include/asm/hyperv-tlfs.h | 338 ++++++++++++++++++++ arch/arm64/include/asm/mshyperv.h | 116 +++++++ arch/x86/include/asm/mshyperv.h | 4 + drivers/hv/Kconfig | 3 +- drivers/hv/hv.c | 2 + include/asm-generic/mshyperv.h | 240 +++++++++++++++ 12 files changed, 1382 insertions(+), 1 deletion(-) create mode 100644 arch/arm64/hyperv/Makefile create mode 100644 arch/arm64/hyperv/hv_hvc.S create mode 100644 arch/arm64/hyperv/hv_init.c create mode 100644 arch/arm64/hyperv/mshyperv.c create mode 100644 arch/arm64/include/asm/hyperv-tlfs.h create mode 100644 arch/arm64/include/asm/mshyperv.h create mode 100644 include/asm-generic/mshyperv.h -- 2.19.1