From patchwork Sun Apr 16 14:32:07 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Julien Grall X-Patchwork-Id: 13213009 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 38A10C77B73 for ; Sun, 16 Apr 2023 14:32:52 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.521562.810315 (Exim 4.92) (envelope-from ) id 1po3Qd-0004an-8x; Sun, 16 Apr 2023 14:32:31 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 521562.810315; Sun, 16 Apr 2023 14:32:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1po3Qd-0004ag-5n; Sun, 16 Apr 2023 14:32:31 +0000 Received: by outflank-mailman (input) for mailman id 521562; Sun, 16 Apr 2023 14:32:30 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1po3Qc-0004Vb-Fm for xen-devel@lists.xenproject.org; Sun, 16 Apr 2023 14:32:30 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1po3Qc-0004yh-4v; Sun, 16 Apr 2023 14:32:30 +0000 Received: from 54-240-197-232.amazon.com ([54.240.197.232] helo=dev-dsk-jgrall-1b-035652ec.eu-west-1.amazon.com) by xenbits.xenproject.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1po3Qb-0008OW-Sa; Sun, 16 Apr 2023 14:32:30 +0000 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" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:MIME-Version:References: In-Reply-To:Message-Id:Date:Subject:Cc:To:From; bh=cmPpxvjkrxWFma6zTaRewwdEQPiJX9jNoQsgck6jnCg=; b=Ar/he/eeHYx7LDhVsytD0xoHaB S6IqcvMjyjBF9tUOme/pTwD7kgJGvxsK7QMExWVNcpLQeYk5vvKJR6V9QeNG05NWcUMjp3JvpVjOQ mlNR8x+7ltvWuv3oiEtOFnuag/etvQQEo16wVxX1jdy4gEOmqJN36Wszou3XzA+9rAxI=; From: Julien Grall To: xen-devel@lists.xenproject.org Cc: Luca.Fancellu@arm.com, michal.orzel@amd.com, Julien Grall , Stefano Stabellini , Julien Grall , Bertrand Marquis , Volodymyr Babchuk , Henry Wang Subject: [PATCH v7 1/5] xen/arm32: head: Widen the use of the temporary mapping Date: Sun, 16 Apr 2023 15:32:07 +0100 Message-Id: <20230416143211.72227-2-julien@xen.org> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20230416143211.72227-1-julien@xen.org> References: <20230416143211.72227-1-julien@xen.org> MIME-Version: 1.0 From: Julien Grall At the moment, the temporary mapping is only used when the virtual runtime region of Xen is clashing with the physical region. In follow-up patches, we will rework how secondary CPU bring-up works and it will be convenient to use the fixmap area for accessing the root page-table (it is per-cpu). Rework the code to use temporary mapping when the Xen physical address is not overlapping with the temporary mapping. This also has the advantage to simplify the logic to identity map Xen. Signed-off-by: Julien Grall Reviewed-by: Henry Wang Tested-by: Henry Wang Reviewed-by: Michal Orzel ---- Even if this patch is rewriting part of the previous patch, I decided to keep them separated to help the review. The "follow-up patches" are still in draft at the moment. I still haven't find a way to split them nicely and not require too much more work in the coloring side. I have provided some medium-term goal in the cover letter. Changes in v6: - Add Henry's reviewed-by and tested-by tag - Add Michal's reviewed-by - Add newline in remove_identity_mapping for clarity Changes in v5: - Fix typo in a comment - No need to link boot_{second, third}_id again if we need to create a temporary area. Changes in v3: - Resolve conflicts after switching from "ldr rX,