From: Gavin Shan <gshan@redhat.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
will@kernel.org, robin.murphy@arm.com, catalin.marinas@arm.com
Cc: maz@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
aneesh.kumar@kernel.org, steven.price@arm.com,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Christoph Hellwig <hch@lst.de>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH v2 3/3] arm64: realm: Use aliased addresses for device DMA to shared buffers
Date: Tue, 25 Feb 2025 15:24:38 +1000 [thread overview]
Message-ID: <c710a9d6-bd1b-4867-bdc9-b3a79e577d0e@redhat.com> (raw)
In-Reply-To: <20250219220751.1276854-4-suzuki.poulose@arm.com>
Hi Suzuki,
On 2/20/25 8:07 AM, Suzuki K Poulose wrote:
> When a device performs DMA to a shared buffer using physical addresses,
> (without Stage1 translation), the device must use the "{I}PA address" with the
> top bit set in Realm. This is to make sure that a trusted device will be able
> to write to shared buffers as well as the protected buffers. Thus, a Realm must
> always program the full address including the "protection" bit, like AMD SME
> encryption bits.
>
> Enable this by providing arm64 specific dma_{encrypted,decrypted,clear_encryption}
> helpers for Realms. Please note that the VMM needs to similarly make sure that
> the SMMU Stage2 in the Non-secure world is setup accordingly to map IPA at the
> unprotected alias.
>
> Cc: Will Deacon <will@kernel.org>
> Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Steven Price <steven.price@arm.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Cc: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> ---
> arch/arm64/include/asm/mem_encrypt.h | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/arch/arm64/include/asm/mem_encrypt.h b/arch/arm64/include/asm/mem_encrypt.h
> index f8f78f622dd2..aeda3bba255e 100644
> --- a/arch/arm64/include/asm/mem_encrypt.h
> +++ b/arch/arm64/include/asm/mem_encrypt.h
> @@ -21,4 +21,26 @@ static inline bool force_dma_unencrypted(struct device *dev)
> return is_realm_world();
> }
>
> +static inline dma_addr_t dma_decrypted(dma_addr_t daddr)
> +{
> + if (is_realm_world())
> + daddr |= prot_ns_shared;
> + return daddr;
> +}
> +#define dma_decrypted dma_decrypted
> +
There is an existing macro (PROT_NS_SHARED), which is preferred to return
prot_ns_shared or 0 depending on the availability of the realm capability.
However, that macro needs to be improved a bit so that it can be used here.
We need to return 0UL to match with the type of prot_ns_shared (unsigned long)
-#define PROT_NS_SHARED (is_realm_world() ? prot_ns_shared : 0)
+#define PROT_NS_SHARED (is_realm_world() ? prot_ns_shared : 0UL)
After that, the chunk of code can be as below.
return daddr | PROT_NS_SHARED;
> +static inline dma_addr_t dma_encrypted(dma_addr_t daddr)
> +{
> + if (is_realm_world())
> + daddr &= prot_ns_shared - 1;
> + return daddr;
> +}
> +#define dma_encrypted dma_encrypted
> +
With PROT_NS_SHARED, it can become something like below. (PROT_NS_SHARED - 1)
is equivalent to -1UL, 'daddr & -1UL' should be fine since it does nothing.
return daddr & (PROT_NS_SHARED - 1);
> +static inline dma_addr_t dma_clear_encryption(dma_addr_t daddr)
> +{
> + return dma_encrypted(daddr);
> +}
> +#define dma_clear_encryption dma_clear_encryption
> +
> #endif /* __ASM_MEM_ENCRYPT_H */
Thanks,
Gavin
next prev parent reply other threads:[~2025-02-25 5:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 22:07 [PATCH v2 0/3] arm64: realm: Fix DMA address for devices Suzuki K Poulose
2025-02-19 22:07 ` [PATCH v2 1/3] dma: Fix encryption bit clearing for dma_to_phys Suzuki K Poulose
2025-02-25 11:25 ` Robin Murphy
2025-02-25 14:04 ` Suzuki K Poulose
2025-02-25 15:26 ` Tom Lendacky
2025-02-19 22:07 ` [PATCH v2 2/3] dma: Introduce generic dma_decrypted/dma_encrypted helpers Suzuki K Poulose
2025-02-25 12:49 ` Robin Murphy
2025-02-25 16:30 ` Suzuki K Poulose
2025-02-19 22:07 ` [PATCH v2 3/3] arm64: realm: Use aliased addresses for device DMA to shared buffers Suzuki K Poulose
2025-02-25 5:24 ` Gavin Shan [this message]
2025-02-25 5:28 ` Gavin Shan
2025-02-25 16:31 ` Suzuki K Poulose
2025-02-25 13:04 ` Robin Murphy
2025-02-25 16:14 ` Suzuki K Poulose
2025-02-26 10:00 ` 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=c710a9d6-bd1b-4867-bdc9-b3a79e577d0e@redhat.com \
--to=gshan@redhat.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jean-philippe@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thomas.lendacky@amd.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