mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: will@kernel.org, catalin.marinas@arm.com, sami.mujawar@arm.com,
	aneesh.kumar@kernel.org, steven.price@arm.com,
	linux-kernel@vger.kernel.org, sudeep.holla@arm.com
Subject: Re: [PATCH 0/3] arm64: realm: Add support for encrypted data from firmware
Date: Mon, 16 Jun 2025 12:15:33 +0100	[thread overview]
Message-ID: <55346820-fbca-4b23-824e-89483601bf61@arm.com> (raw)
In-Reply-To: <20250613111153.1548928-1-suzuki.poulose@arm.com>

On 13/06/2025 12:11, Suzuki K Poulose wrote:
> Confidential compute firmware may provide secret data via reserved memory regions
> (e.g., ACPI CCEL, EFI Coco secret area). These must be ioremap'ed() as encrypted.
> As of now, realm only maps "trusted devices" (RIPAS = RSI_RIPAS_DEV) as encrypted.
> This series adds support for mapping areas that are protected
> (i.e., RIPAS = RSI_RIPAS_RAM) as encrypted. Also, extrapolating that, we can map
> anything that is not RIPAS_EMPTY as protected, as it is guaranteed to be "protected".
> 
> With this in place, we can naturally map any firmware provided area based on the
> RIPAS value. If the firmware provides a shared region (not trusted), it must have
> set the RIPAS accordingly, before placing the data, as the transition is always
> destructive.
> 
> Also enables the EFI Coco secret area support and Confidential Compute Event
> Log (CCEL) for arm64.
> 

A branch with the patches is also available here:

git@git.gitlab.arm.com:linux-arm/linux-cca.git  cca-guest/coco-secret/v1


Suzuki


> 
> Suzuki K Poulose (3):
>    arm64: realm: ioremap: Allow mapping memory as encrypted
>    arm64: Enable EFI secret area Securityfs support
>    arm64: acpi: Enable ACPI CCEL support
> 
>   arch/arm64/include/asm/io.h          |  6 +++++-
>   arch/arm64/include/asm/rsi.h         |  2 +-
>   arch/arm64/kernel/acpi.c             |  5 +++++
>   arch/arm64/kernel/rsi.c              | 26 ++++++++++++++++++++++----
>   drivers/virt/coco/efi_secret/Kconfig |  2 +-
>   5 files changed, 34 insertions(+), 7 deletions(-)
> 


  parent reply	other threads:[~2025-06-16 11:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 11:11 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
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 ` Suzuki K Poulose [this message]
2025-06-17  9:20   ` [PATCH 0/3] arm64: realm: Add support for encrypted data from firmware 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=55346820-fbca-4b23-824e-89483601bf61@arm.com \
    --to=suzuki.poulose@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=steven.price@arm.com \
    --cc=sudeep.holla@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®