From: Steven Price <steven.price@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: will@kernel.org, catalin.marinas@arm.com, sami.mujawar@arm.com,
aneesh.kumar@kernel.org, linux-kernel@vger.kernel.org,
sudeep.holla@arm.com
Subject: Re: [PATCH 1/3] arm64: realm: ioremap: Allow mapping memory as encrypted
Date: Wed, 18 Jun 2025 16:02:41 +0100 [thread overview]
Message-ID: <bc8a73d2-ba85-4431-a8e9-3692cc1e402a@arm.com> (raw)
In-Reply-To: <20250613111153.1548928-2-suzuki.poulose@arm.com>
On 13/06/2025 12:11, Suzuki K Poulose wrote:
> For ioremap(), so far we only checked if it was a device (RIPAS_DEV) to choose
> an encrypted vs decrypted mapping. However, we may have firmware reserved memory
> regions exposed to the OS (e.g., EFI Coco Secret Securityfs, ACPI CCEL).
> We need to make sure that anything that is RIPAS_RAM (i.e., Guest
> protected memory with RMM guarantees) are also mapped as encrypted.
>
> Rephrasing the above, anything that is not RIPAS_EMPTY is guaranteed to be
> protected by the RMM. Thus we choose encrypted mapping for anything that is not
> RIPAS_EMPTY. While at it, rename the helper function
>
> __arm64_is_protected_mmio => arm64_rsi_is_protected
>
> to clearly indicate that this not an arm64 generic helper, but something to do
> with Realms.
>
> Cc: Sami Mujawar <sami.mujawar@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>
> Cc: Steven Price <steven.price@arm.com>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> arch/arm64/include/asm/io.h | 2 +-
> arch/arm64/include/asm/rsi.h | 2 +-
> arch/arm64/kernel/rsi.c | 26 ++++++++++++++++++++++----
> 3 files changed, 24 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/include/asm/io.h b/arch/arm64/include/asm/io.h
> index 9b96840fb979..82276282a3c7 100644
> --- a/arch/arm64/include/asm/io.h
> +++ b/arch/arm64/include/asm/io.h
> @@ -311,7 +311,7 @@ extern bool arch_memremap_can_ram_remap(resource_size_t offset, size_t size,
> static inline bool arm64_is_protected_mmio(phys_addr_t phys_addr, size_t size)
> {
> if (unlikely(is_realm_world()))
> - return __arm64_is_protected_mmio(phys_addr, size);
> + return arm64_rsi_is_protected(phys_addr, size);
> return false;
> }
>
> diff --git a/arch/arm64/include/asm/rsi.h b/arch/arm64/include/asm/rsi.h
> index b42aeac05340..88b50d660e85 100644
> --- a/arch/arm64/include/asm/rsi.h
> +++ b/arch/arm64/include/asm/rsi.h
> @@ -16,7 +16,7 @@ DECLARE_STATIC_KEY_FALSE(rsi_present);
>
> void __init arm64_rsi_init(void);
>
> -bool __arm64_is_protected_mmio(phys_addr_t base, size_t size);
> +bool arm64_rsi_is_protected(phys_addr_t base, size_t size);
>
> static inline bool is_realm_world(void)
> {
> diff --git a/arch/arm64/kernel/rsi.c b/arch/arm64/kernel/rsi.c
> index ce4778141ec7..c64a06f58c0b 100644
> --- a/arch/arm64/kernel/rsi.c
> +++ b/arch/arm64/kernel/rsi.c
> @@ -84,7 +84,25 @@ static void __init arm64_rsi_setup_memory(void)
> }
> }
>
> -bool __arm64_is_protected_mmio(phys_addr_t base, size_t size)
> +/*
> + * Check if a given PA range is Trusted (e.g., Protected memory, a Trusted Device
> + * mapping, or an MMIO emulated in the Realm world).
> + *
> + * We can rely on the RIPAS value of the region to detect if a given region is
> + * protected.
> + *
> + * RIPAS_DEV - A trusted device memory or a trusted emulated MMIO (in the Realm
> + * world
> + * RIPAS_RAM - Memory (RAM), protected by the RMM guarantees. (e.g., Firmware
> + * reserved regions for data sharing).
> + *
> + * RIPAS_DESTROYED is a special case of one of the above, where the host did
> + * something without our permission and as such we can't do anything about it.
> + *
> + * The only case where something is emulated by the untrusted hypervisor or is
> + * backed by shared memory is indicated by RSI_RIPAS_EMPTY.
> + */
> +bool arm64_rsi_is_protected(phys_addr_t base, size_t size)
> {
> enum ripas ripas;
> phys_addr_t end, top;
> @@ -101,18 +119,18 @@ bool __arm64_is_protected_mmio(phys_addr_t base, size_t size)
> break;
> if (WARN_ON(top <= base))
> break;
> - if (ripas != RSI_RIPAS_DEV)
> + if (ripas == RSI_RIPAS_EMPTY)
> break;
> base = top;
> }
>
> return base >= end;
> }
> -EXPORT_SYMBOL(__arm64_is_protected_mmio);
> +EXPORT_SYMBOL(arm64_rsi_is_protected);
>
> static int realm_ioremap_hook(phys_addr_t phys, size_t size, pgprot_t *prot)
> {
> - if (__arm64_is_protected_mmio(phys, size))
> + if (arm64_rsi_is_protected(phys, size))
> *prot = pgprot_encrypted(*prot);
> else
> *prot = pgprot_decrypted(*prot);
next prev parent reply other threads:[~2025-06-18 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:11 [PATCH 0/3] arm64: realm: Add support for encrypted data from firmware Suzuki K Poulose
2025-06-13 11:11 ` [PATCH 1/3] arm64: realm: ioremap: Allow mapping memory as encrypted Suzuki K Poulose
2025-06-18 15:02 ` Steven Price [this message]
2025-06-30 1:33 ` Gavin Shan
2025-06-13 11:11 ` [PATCH 2/3] arm64: Enable EFI secret area Securityfs support Suzuki K Poulose
2025-06-30 1:34 ` Gavin Shan
2025-06-13 11:11 ` [PATCH 3/3] arm64: acpi: Enable ACPI CCEL support Suzuki K Poulose
2025-06-30 1:34 ` Gavin Shan
2025-07-15 13:56 ` Will Deacon
2025-07-15 14:38 ` Suzuki K Poulose
2025-07-15 14:58 ` Will Deacon
2025-07-25 11:09 ` Suzuki K Poulose
2025-06-16 11:15 ` [PATCH 0/3] arm64: realm: Add support for encrypted data from firmware Suzuki K Poulose
2025-06-17 9:20 ` Sami Mujawar
2025-07-09 12:53 ` Suzuki K Poulose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc8a73d2-ba85-4431-a8e9-3692cc1e402a@arm.com \
--to=steven.price@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sami.mujawar@arm.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®