From mboxrd@z Thu Jan 1 00:00:00 1970 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 lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (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 D53C2C433F5 for ; Thu, 24 Feb 2022 01:30:57 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.277852.474695 (Exim 4.92) (envelope-from ) id 1nN2xo-0005yS-Ov; Thu, 24 Feb 2022 01:30:36 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 277852.474695; Thu, 24 Feb 2022 01:30:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nN2xo-0005yL-H3; Thu, 24 Feb 2022 01:30:36 +0000 Received: by outflank-mailman (input) for mailman id 277852; Thu, 24 Feb 2022 01:30:34 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nN2xm-0005xm-PN for xen-devel@lists.xenproject.org; Thu, 24 Feb 2022 01:30:34 +0000 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by se1-gles-flk1.inumbo.com (Halon) with ESMTP id 5add9651-9511-11ec-8539-5f4723681683; Thu, 24 Feb 2022 02:30:32 +0100 (CET) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E279C1063; Wed, 23 Feb 2022 17:30:30 -0800 (PST) Received: from entos-skylake.shanghai.arm.com (entos-skylake.shanghai.arm.com [10.169.212.207]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 8671B3F5A1; Wed, 23 Feb 2022 17:30:28 -0800 (PST) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 5add9651-9511-11ec-8539-5f4723681683 From: Henry Wang To: xen-devel@lists.xenproject.org, sstabellini@kernel.org, julien@xen.org Cc: Bertrand.Marquis@arm.com, wei.chen@arm.com, penny.zheng@arm.com, Henry.Wang@arm.com Subject: [RFC PATCH 0/2] Introduce reserved Xenheap Date: Thu, 24 Feb 2022 01:30:21 +0000 Message-Id: <20220224013023.50920-1-Henry.Wang@arm.com> X-Mailer: git-send-email 2.17.1 The reserved Xenheap, or statically configured Xenheap, refers to parts of RAM reserved in the beginning for Xenheap. Like the static memory allocation, such reserved Xenheap regions are reserved by configuration in the device tree using physical address ranges. This feature is useful to run Xen on Arm MPU systems, where only a finite number of memory protection regions are available. The limited number of protection regions places requirement on planning the use of MPU protection regions and one or more MPU protection regions needs to be reserved only for Xenheap. Therefore, this patch series is sent as RFC for comments from the community. The first patch introduces the reserved Xenheap and the device tree processing code. The second patch adds the implementation of the reserved Xenheap pages handling in boot and heap allocator on Arm64. Henry Wang (2): docs, xen/arm: Introduce reserved Xenheap memory xen/arm: Handle reserved Xenheap pages in boot/heap allocator docs/misc/arm/device-tree/booting.txt | 43 ++++++++++++++++++++++ xen/arch/arm/bootfdt.c | 52 +++++++++++++++++++++------ xen/arch/arm/include/asm/setup.h | 3 ++ xen/arch/arm/setup.c | 52 +++++++++++++++++++-------- 4 files changed, 125 insertions(+), 25 deletions(-) -- 2.17.1