From patchwork Thu Apr 14 19:19:27 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Oleksandr Tyshchenko X-Patchwork-Id: 12813942 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EC57EC433EF for ; Thu, 14 Apr 2022 19:20:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=oh7tGVDNrAZwoqBqmJDBaeLykjsbxSvdRfpgZKW2v8c=; b=fk3WoggG6nHMO3 XbniZ1tBvqcYwiPT9XKGu6DAmpwsVfxlIlzanj6OOy+YIdy+z2UOd9ZM+Om0YoAD150eBGNNFfl69 ZRrUr9gxqYn1iOvnQ6yf+VnVq+hTJhk5/Cv0usf2PhczvlvZsIyYGBcWyEweolru2b5RZK+unXfYc wLdIUMRCpsmkQKpm6cawM2Ilt/fxrxI/p7ruFBVlRpXTN4n0qicKkT9u/TzHyR69y+Qey/HaxEjQ5 65FBX1jZDlW9yGfuTVk1RXPrqepsH67mc8bi2aL+JEkoHYn6+keq3HevkyZMzgV5zjdRNY0tw1PXJ LzbTBar/k0mFSfcCcGaQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nf50L-0071w5-CY; Thu, 14 Apr 2022 19:19:45 +0000 Received: from mail-lf1-x135.google.com ([2a00:1450:4864:20::135]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nf50H-0071vA-G1 for linux-arm-kernel@lists.infradead.org; Thu, 14 Apr 2022 19:19:43 +0000 Received: by mail-lf1-x135.google.com with SMTP id u19so10776189lff.4 for ; Thu, 14 Apr 2022 12:19:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=hBeYUJyh8cohFIBXMw+rp2zvHseFstsvrmjjJq6v1RA=; b=OS9Zyyw11+ahcSbaFBwnet4m/+SqFvTSxBJAra7HuBWht0AJqsov+byDRY2fDcE7Cs ytQj6zRGrqwIncCbAZw9crMvkswQ0zpZovlwDav7PgeiWph9GDH1Vn+lFgWyfq4pf9Q6 D2bG8OWhifqZbowaCdO0dbVut/XPPk2sn+J4gDQPfI0IRUkzB49h1qS2s77WM2wj6Hc0 XiiWyRzeOYZiYXi7x7A/rRQlZHH+glMqunBBbrU6BwKqFdu1m5oH6E29FDom7ZKFAHyW 2ozw4PRAgrtB8ITcoMnvHW1txGeX3p4mnMFmtLnTd+4XkolWYRvNXGTibUY+EzZSgMXW D3vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=hBeYUJyh8cohFIBXMw+rp2zvHseFstsvrmjjJq6v1RA=; b=2+qsOr94TQIcniWlDNmc52qKfFHx3SgfyOoDb/3FqkTOaJvNHtwOkgHvVikpBGvQG3 l7okjGtGPP1sMN0Qo1PRr2Clb58XOYFCSZWtsoLsSVcMFqHdeqCl4543k7tTK2c/HtnP l86Q++ytdd6V6mcs6ovHrsvPZ9TwL2q8R5fAysKy9JmN8LleOFko2BNIpkapkPJSui5j SB4gFUsXXqOZHEpd5CYUGPskLhb4S57CWQJnVaW3FYPoijUTBpSC8HHbn2bZuVU9cQCL 2RDlcJsOV7cklpfjCKV4TYbw6b/Nau1Eb59vax6DPGW9oJ81PEBdSsWgb4oWLN937P6e SyPA== X-Gm-Message-State: AOAM531GpsZHlkYOzXkqaIJzet4mkAguP27NZTalWj1XsJ15YXZfJoJk IhR+nESsLaPN7TnlyuRHkhg= X-Google-Smtp-Source: ABdhPJyF5XrQhJyJg+R3ILmVTNsDHntbRwzflHI2RtvXh6tjp4CUiSxKClbc5XPs/9iS6Kt3RoSWZQ== X-Received: by 2002:ac2:4d18:0:b0:46b:c318:193b with SMTP id r24-20020ac24d18000000b0046bc318193bmr2602821lfi.293.1649963978137; Thu, 14 Apr 2022 12:19:38 -0700 (PDT) Received: from otyshchenko.router ([212.22.223.21]) by smtp.gmail.com with ESMTPSA id l3-20020a194943000000b0046b928d2795sm85001lfj.67.2022.04.14.12.19.36 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Apr 2022 12:19:37 -0700 (PDT) From: Oleksandr Tyshchenko To: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, virtualization@lists.linux-foundation.org Cc: Oleksandr Tyshchenko , "Michael S. Tsirkin" , Stefano Stabellini , Boris Ostrovsky , Juergen Gross , Julien Grall , Bertrand Marquis , Wei Chen , Henry Wang , Kaly Xin , Jiamei Xie , =?utf-8?q?Alex_Benn=C3=A9e?= Subject: [RFC PATCH 0/6] virtio: Solution to restrict memory access under Xen using xen-virtio DMA ops layer Date: Thu, 14 Apr 2022 22:19:27 +0300 Message-Id: <1649963973-22879-1-git-send-email-olekstysh@gmail.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220414_121941_583397_C5F6C395 X-CRM114-Status: GOOD ( 23.54 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org From: Oleksandr Tyshchenko Hello all. The purpose of this RFC patch series is to add support for restricting memory access under Xen using specific grant table based DMA ops layer. Patch series is based on Juergen Gross’ initial work [1] which implies using grant references instead of raw guest physical addresses (GPA) for the virtio communications (some kind of the software IOMMU). The high level idea is to create new Xen’s grant table based DMA ops layer for the guest Linux whose main purpose is to provide a special 64-bit DMA address which is formed by using the grant reference (for a page to be shared with the backend) with offset and setting the highest address bit (this is for the backend to be able to distinguish grant ref based DMA address from normal GPA). For this to work we need the ability to allocate contiguous (consecutive) grant references for multi-page allocations. And the backend then needs to offer VIRTIO_F_ACCESS_PLATFORM and VIRTIO_F_VERSION_1 feature bits (it must support virtio-mmio modern transport for 64-bit addresses in the virtqueue). Xen's grant mapping mechanism is the secure and safe solution to share pages between domains which proven to work and works for years (in the context of traditional Xen PV drivers for example). So far, the foreign mapping is used for the virtio backend to map and access guest memory. With the foreign mapping, the backend is able to map arbitrary pages from the guest memory (or even from Dom0 memory). And as the result, the malicious backend which runs in a non-trusted domain can take advantage of this. Instead, with the grant mapping the backend is only allowed to map pages which were explicitly granted by the guest before and nothing else. According to the discussions in various mainline threads this solution would likely be welcome because it perfectly fits in the security model Xen provides. What is more, the grant table based solution requires zero changes to the Xen hypervisor itself at least with virtio-mmio and DT (in comparison, for example, with "foreign mapping + virtio-iommu" solution which would require the whole new complex emulator in hypervisor in addition to new functionality/hypercall to pass IOVA from the virtio backend running elsewhere to the hypervisor and translate it to the GPA before mapping into P2M or denying the foreign mapping request if no corresponding IOVA-GPA mapping present in the IOMMU page table for that particular device). We only need to update toolstack to insert a new "xen,dev-domid" property to the virtio-mmio device node when creating a guest device-tree (this is an indicator for the guest to use grants and the ID of Xen domain where the corresponding backend resides, it is used as an argument to the grant mapping APIs). It worth mentioning that toolstack patch is based on non upstreamed yet “Virtio support for toolstack on Arm” series which is on review now [2]. Please note the following: - Patch series only covers Arm and virtio-mmio (device-tree) for now. To enable the restricted memory access feature on Arm the following options should be set: CONFIG_XEN_VIRTIO = y CONFIG_XEN_HVM_VIRTIO_GRANT = y - Some callbacks in xen-virtio DMA ops layer (map_sg/unmap_sg, etc) are not implemented yet as they are not needed/used in the first prototype Patch series is rebased on Linux 5.18-rc2 tag and tested on Renesas Salvator-X board + H3 ES3.0 SoC (Arm64) with standalone userspace (non-Qemu) virtio-mmio based virtio-disk backend running in Driver domain and Linux guest running on existing virtio-blk driver (frontend). No issues were observed. Guest domain 'reboot/destroy' use-cases work properly. I have also tested other use-cases such as assigning several virtio block devices or a mix of virtio and Xen PV block devices to the guest. 1. Xen changes located at (last patch): https://github.com/otyshchenko1/xen/commits/libxl_virtio_next 2. Linux changes located at: https://github.com/otyshchenko1/linux/commits/virtio_grant5 3. virtio-disk changes located at: https://github.com/otyshchenko1/virtio-disk/commits/virtio_grant Any feedback/help would be highly appreciated. [1] https://www.youtube.com/watch?v=IrlEdaIUDPk [2] https://lore.kernel.org/xen-devel/1649442065-8332-1-git-send-email-olekstysh@gmail.com/ Juergen Gross (2): xen/grants: support allocating consecutive grants virtio: add option to restrict memory access under Xen Oleksandr Tyshchenko (4): dt-bindings: xen: Add xen,dev-domid property description for xen-virtio layer virtio: Various updates to xen-virtio DMA ops layer arm/xen: Introduce xen_setup_dma_ops() arm/xen: Assign xen-virtio DMA ops for virtio devices in Xen guests .../devicetree/bindings/virtio/xen,dev-domid.yaml | 39 +++ arch/arm/include/asm/xen/xen-ops.h | 1 + arch/arm/mm/dma-mapping.c | 5 +- arch/arm/xen/enlighten.c | 11 + arch/arm64/include/asm/xen/xen-ops.h | 1 + arch/arm64/mm/dma-mapping.c | 5 +- arch/x86/mm/init.c | 15 + arch/x86/mm/mem_encrypt.c | 5 - arch/x86/xen/Kconfig | 9 + drivers/xen/Kconfig | 20 ++ drivers/xen/Makefile | 1 + drivers/xen/grant-table.c | 238 +++++++++++++-- drivers/xen/xen-virtio.c | 335 +++++++++++++++++++++ include/xen/arm/xen-ops.h | 20 ++ include/xen/grant_table.h | 4 + include/xen/xen-ops.h | 13 + 16 files changed, 679 insertions(+), 43 deletions(-) create mode 100644 Documentation/devicetree/bindings/virtio/xen,dev-domid.yaml create mode 100644 arch/arm/include/asm/xen/xen-ops.h create mode 100644 arch/arm64/include/asm/xen/xen-ops.h create mode 100644 drivers/xen/xen-virtio.c create mode 100644 include/xen/arm/xen-ops.h