From: Robin Murphy <robin.murphy@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>, linux-kernel@vger.kernel.org
Cc: will@kernel.org, catalin.marinas@arm.com, maz@kernel.org,
steven.price@arm.com, aneesh.kumar@kernel.org, gshan@redhat.com,
linux-arm-kernel@lists.infradead.org,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH v3 2/3] dma: Introduce generic dma_addr_*crypted helpers
Date: Fri, 28 Feb 2025 18:23:41 +0000 [thread overview]
Message-ID: <4f057e37-7f6c-4daa-b99a-122aa417f0e3@arm.com> (raw)
In-Reply-To: <20250227144150.1667735-3-suzuki.poulose@arm.com>
On 27/02/2025 2:41 pm, Suzuki K Poulose wrote:
> AMD SME added __sme_set/__sme_clr primitives to modify the DMA address for
> encrypted/decrypted traffic. However this doesn't fit in with other models,
> e.g., Arm CCA where the meanings are the opposite. i.e., "decrypted" traffic
> has a bit set and "encrypted" traffic has the top bit cleared.
>
> In preparation for adding the support for Arm CCA DMA conversions, convert the
> existing primitives to more generic ones that can be provided by the backends.
> i.e., add helpers to
> 1. dma_addr_encrypted - Convert a DMA address to "encrypted" [ == __sme_set() ]
> 2. dma_addr_unencrypted - Convert a DMA address to "decrypted" [ None exists today ]
> 3. dma_addr_canonical - Clear any "encryption"/"decryption" bits from DMA
> address [ SME uses __sme_clr() ] and convert to a canonical DMA address.
>
> Since the original __sme_xxx helpers come from linux/mem_encrypt.h, use that
> as the home for the new definitions and provide dummy ones when none is provided
> by the architectures.
>
> With the above, phys_to_dma_unencrypted() uses the newly added dma_addr_unencrypted()
> helper and to make it a bit more easier to read and avoid double conversion,
> provide __phys_to_dma().
Yeah, I'm happy with "canonical" being the least-worst option for now; I
certainly can't think of anything snappier yet still sufficiently clear.
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Suggested-by: Robin Murphy <robin.murphy@arm.com>
> 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: Marek Szyprowski <m.szyprowski@samsung.com>
> 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>
> ---
> Changes since v2:
> - Rename helpers- s/dma_*crypted/dma_addr_*crypted (Robin)
> ---
> include/linux/dma-direct.h | 12 ++++++++----
> include/linux/mem_encrypt.h | 23 +++++++++++++++++++++++
> 2 files changed, 31 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/dma-direct.h b/include/linux/dma-direct.h
> index d20ecc24cb0f..f3bc0bcd7098 100644
> --- a/include/linux/dma-direct.h
> +++ b/include/linux/dma-direct.h
> @@ -78,14 +78,18 @@ static inline dma_addr_t dma_range_map_max(const struct bus_dma_region *map)
> #define phys_to_dma_unencrypted phys_to_dma
> #endif
> #else
> -static inline dma_addr_t phys_to_dma_unencrypted(struct device *dev,
> - phys_addr_t paddr)
> +static inline dma_addr_t __phys_to_dma(struct device *dev, phys_addr_t paddr)
> {
> if (dev->dma_range_map)
> return translate_phys_to_dma(dev, paddr);
> return paddr;
> }
>
> +static inline dma_addr_t phys_to_dma_unencrypted(struct device *dev,
> + phys_addr_t paddr)
> +{
> + return dma_addr_unencrypted(__phys_to_dma(dev, paddr));
> +}
> /*
> * If memory encryption is supported, phys_to_dma will set the memory encryption
> * bit in the DMA address, and dma_to_phys will clear it.
> @@ -94,14 +98,14 @@ static inline dma_addr_t phys_to_dma_unencrypted(struct device *dev,
> */
> static inline dma_addr_t phys_to_dma(struct device *dev, phys_addr_t paddr)
> {
> - return __sme_set(phys_to_dma_unencrypted(dev, paddr));
> + return dma_addr_encrypted(__phys_to_dma(dev, paddr));
> }
>
> static inline phys_addr_t dma_to_phys(struct device *dev, dma_addr_t dma_addr)
> {
> phys_addr_t paddr;
>
> - dma_addr = __sme_clr(dma_addr);
> + dma_addr = dma_addr_canonical(dma_addr);
> if (dev->dma_range_map)
> paddr = translate_dma_to_phys(dev, dma_addr);
> else
> diff --git a/include/linux/mem_encrypt.h b/include/linux/mem_encrypt.h
> index ae4526389261..07584c5e36fb 100644
> --- a/include/linux/mem_encrypt.h
> +++ b/include/linux/mem_encrypt.h
> @@ -26,11 +26,34 @@
> */
> #define __sme_set(x) ((x) | sme_me_mask)
> #define __sme_clr(x) ((x) & ~sme_me_mask)
> +
> +#define dma_addr_encrypted(x) __sme_set(x)
> +#define dma_addr_canonical(x) __sme_clr(x)
> +
> #else
> #define __sme_set(x) (x)
> #define __sme_clr(x) (x)
> #endif
>
> +/*
> + * dma_addr_encrypted() and dma_addr_unencrypted() are for converting a given DMA
> + * address to the respective type of addressing.
> + *
> + * dma_addr_canonical() is used to reverse any conversions for encrypted/decrypted
> + * back to the canonical address.
> + */
> +#ifndef dma_addr_encrypted
> +#define dma_addr_encrypted(x) (x)
> +#endif
> +
> +#ifndef dma_addr_unencrypted
> +#define dma_addr_unencrypted(x) (x)
> +#endif
> +
> +#ifndef dma_addr_canonical
> +#define dma_addr_canonical(x) (x)
> +#endif
> +
> #endif /* __ASSEMBLY__ */
>
> #endif /* __MEM_ENCRYPT_H__ */
next prev parent reply other threads:[~2025-02-28 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 14:41 [PATCH v3 0/3] arm64: realm: Fix DMA address for devices Suzuki K Poulose
2025-02-27 14:41 ` [PATCH v3 1/3] dma: Fix encryption bit clearing for dma_to_phys Suzuki K Poulose
2025-02-28 2:08 ` Gavin Shan
2025-02-27 14:41 ` [PATCH v3 2/3] dma: Introduce generic dma_addr_*crypted helpers Suzuki K Poulose
2025-02-28 2:09 ` Gavin Shan
2025-02-28 18:23 ` Robin Murphy [this message]
2025-02-27 14:41 ` [PATCH v3 3/3] arm64: realm: Use aliased addresses for device DMA to shared buffers Suzuki K Poulose
2025-02-27 16:05 ` Catalin Marinas
2025-02-27 17:03 ` Suzuki K Poulose
2025-02-28 2:08 ` Gavin Shan
2025-03-03 14:16 ` Robin Murphy
2025-03-03 11:35 ` [PATCH v3 0/3] arm64: realm: Fix DMA address for devices Suzuki K Poulose
2025-03-04 13:40 ` Marek Szyprowski
2025-03-06 11:39 ` Suzuki K Poulose
2025-03-06 18:06 ` Catalin Marinas
2025-03-11 11:45 ` Will Deacon
2025-03-11 17:15 ` Catalin Marinas
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=4f057e37-7f6c-4daa-b99a-122aa417f0e3@arm.com \
--to=robin.murphy@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=hch@lst.de \
--cc=jean-philippe@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maz@kernel.org \
--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
all inboxes | Powered by JetHome®