linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Itaru Kitayama <itaru.kitayama@linux.dev>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
	kvmarm@lists.linux.dev, catalin.marinas@arm.com, will@kernel.org,
	maz@kernel.org, steven.price@arm.com, alexandru.elisei@arm.com,
	joey.gouly@arm.com, james.morse@arm.com,
	Jonathan.Cameron@huawei.com, dgilbert@redhat.com, jpb@kernel.org,
	oliver.upton@linux.dev, zhi.wang.linux@gmail.com,
	yuzenghui@huawei.com, salil.mehta@huawei.com,
	Andrew Jones <andrew.jones@linux.dev>,
	Chao Peng <chao.p.peng@linux.intel.com>,
	Christoffer Dall <christoffer.dall@arm.com>,
	Fuad Tabba <tabba@google.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Quentin Perret <qperret@google.com>,
	Sean Christopherson <seanjc@google.com>,
	Thomas Huth <thuth@redhat.com>,
	Ryan Roberts <Ryan.Roberts@arm.com>,
	Sami Mujawar <Sami.Mujawar@arm.com>
Subject: Re: [RFC] Support for Arm CCA VMs on Linux
Date: Fri, 12 Jan 2024 14:01:47 +0900	[thread overview]
Message-ID: <ZaDHu/zUlazt7i+R@vm3> (raw)
In-Reply-To: <ec8ed5b0-5080-45e9-a4a6-e5dbe48e86d3@arm.com>

On Wed, Jan 10, 2024 at 11:41:09AM +0000, Suzuki K Poulose wrote:
> Hi Itaru,
> 
> On 10/01/2024 05:40, Itaru Kitayama wrote:
> > On Mon, Oct 02, 2023 at 01:43:11PM +0100, Suzuki K Poulose wrote:
> > > Hi,
> > > 
> > > 
> > > > We are happy to announce the early RFC version of the Arm
> > > > Confidential Compute Architecture (CCA) support for the Linux
> > > > stack. The intention is to seek early feedback in the following areas:
> > > >   * KVM integration of the Arm CCA
> > > >   * KVM UABI for managing the Realms, seeking to generalise the operations
> > > >     wherever possible with other Confidential Compute solutions.
> > > >     Note: This version doesn't support Guest Private memory, which will be added
> > > >     later (see below).
> > > >   * Linux Guest support for Realms
> > > > 
> > > 
> > > We have updated the stack for Arm CCA Linux support to RMM-v1.0-EAC2 (See links)
> > > We are not posting the patches for review yet, as we plan to update our
> > > stack to support the latest RMM-v1.0 specification, which includes some
> > > functional changes to support PSCI monitoring by the VMM along with other
> > > minor changes. All relevant components are updated on a new branch "rmm-v1.0-eac2"
> > > Guest-mem support is not included, but is in progress.
> > > 
> > > Change log :
> > >   - KVM RMI support updated to v1.0-eac2, with optimisations to stage2 tear down
> > >   - Guest (Linux and kvm-unit-test) support for RSI compliant to v1.0-eac2
> > >   - SVE, PMU support for Realms
> > > 
> > > kvmtool :
> > >    - Dropped no-compat and switched to --loglevel (merged upstream)
> > >    - Support for SVE, --sve-vl for vector length
> > > 
> > > > Arm CCA Introduction
> > > > =====================
> > > > 
> > > > The Arm CCA is a reference software architecture and implementation that builds
> > > > on the Realm Management Extension (RME), enabling the execution of Virtual
> > > > machines, while preventing access by more privileged software, such as hypervisor.
> > > > The Arm CCA allows the hypervisor to control the VM, but removes the right for
> > > > access to the code, register state or data that is used by VM.
> > > > More information on the architecture is available here[0].
> > > > 
> > > >      Arm CCA Reference Software Architecture
> > > > 
> > > >          Realm World    ||    Normal World   ||  Secure World  ||
> > > >                         ||        |          ||                ||
> > > >   EL0 x-------x         || x----x | x------x ||                ||
> > > >       | Realm |         || |    | | |      | ||                ||
> > > >       |       |         || | VM | | |      | ||                ||
> > > >   ----|  VM*  |---------||-|    |---|      |-||----------------||
> > > >       |       |         || |    | | |  H   | ||                ||
> > > >   EL1 x-------x         || x----x | |      | ||                ||
> > > >           ^             ||        | |  o   | ||                ||
> > > >           |             ||        | |      | ||                ||
> > > >   ------- R*------------------------|  s  -|---------------------
> > > >           S             ||          |      | ||                ||
> > > >           I             ||          |  t   | ||                ||
> > > >           |             ||          |      | ||                ||
> > > >           v             ||          x------x ||                ||
> > > >   EL2    RMM*           ||              ^    ||                ||
> > > >           ^             ||              |    ||                ||
> > > >   ========|=============================|========================
> > > >           |                             | SMC
> > > >           x--------- *RMI* -------------x
> > > > 
> > > >   EL3                   Root World
> > > >                         EL3 Firmware
> > > >   ===============================================================
> > > > Where :
> > > >   RMM - Realm Management Monitor
> > > >   RMI - Realm Management Interface
> > > >   RSI - Realm Service Interface
> > > >   SMC - Secure Monitor Call
> > > > 
> > > > RME introduces a new security state "Realm world", in addition to the
> > > > traditional Secure and Non-Secure states. The Arm CCA defines a new component,
> > > > Realm Management Monitor (RMM) that runs at R-EL2. This is a standard piece of
> > > > firmware, verified, installed and loaded by the EL3 firmware (e.g, TF-A), at
> > > > system boot.
> > > > 
> > > > The RMM provides standard interfaces - Realm Management Interface (RMI) - to the
> > > > Normal world hypervisor to manage the VMs running in the Realm world (also called
> > > > Realms in short). These are exposed via SMC and are routed through the EL3
> > > > firmwre.
> > > > The RMI interface includes:
> > > >    - Move a physical page from the Normal world to the Realm world
> > > >    - Creating a Realm with requested parameters, tracked via Realm Descriptor (RD)
> > > >    - Creating VCPUs aka Realm Execution Context (REC), with initial register state.
> > > >    - Create stage2 translation table at any level.
> > > >    - Load initial images into Realm Memory from normal world memory
> > > >    - Schedule RECs (vCPUs) and handle exits
> > > >    - Inject virtual interrupts into the Realm
> > > >    - Service stage2 runtime faults with pages (provided by host, scrubbed by RMM).
> > > >    - Create "shared" mappings that can be accessed by VMM/Hyp.
> > > >    - Reclaim the memory allocated for the RAM and RTTs (Realm Translation Tables)
> > > > 
> > > > However v1.0 of RMM specifications doesn't support:
> > > >   - Paging protected memory of a Realm VM. Thus the pages backing the protected
> > > >     memory region must be pinned.
> > > >   - Live migration of Realms.
> > > >   - Trusted Device assignment.
> > > >   - Physical interrupt backed Virtual interrupts for Realms
> > > > 
> > > > RMM also provides certain services to the Realms via SMC, called Realm Service
> > > > Interface (RSI). These include:
> > > >   - Realm Guest Configuration.
> > > >   - Attestation & Measurement services
> > > >   - Managing the state of an Intermediate Physical Address (IPA aka GPA) page.
> > > >   - Host Call service (Communication with the Normal world Hypervisor)
> > > > 
> > > > The specifications for the RMM software is currently at *v1.0-Beta2* and the
> > > > latest version is available here [1].
> > > > 
> > > > The Trusted Firmware foundation has an implementation of the RMM - TF-RMM -
> > > > available here [3].
> > > > 
> > > > Implementation
> > > > =================
> > > > 
> > > > This version of the stack is based on the RMM specification v1.0-Beta0[2], with
> > > > following exceptions :
> > > >    - TF-RMM/KVM currently doesn't support the optional features of PMU,
> > > >       SVE and Self-hosted debug (coming soon).
> > > >    - The RSI_HOST_CALL structure alignment requirement is reduced to match
> > > >       RMM v1.0 Beta1
> > > >    - RMI/RSI version numbers do not match the RMM spec. This will be
> > > >      resolved once the spec/implementation is complete, across TF-RMM+Linux stack.
> > > > 
> > > > We plan to update the stack to support the latest version of the RMMv1.0 spec
> > > > in the coming revisions.
> > > > 
> > > > This release includes the following components :
> > > > 
> > > >   a) Linux Kernel
> > > >       i) Host / KVM support - Support for driving the Realms via RMI. This is
> > > >       dependent on running in the Kernel at EL2 (aka VHE mode). Also provides
> > > >       UABI for VMMs to manage the Realm VMs. The support is restricted to 4K page
> > > >       size, matching the Stage2 granule supported by RMM. The VMM is responsible
> > > >       for making sure the guest memory is locked.
> > > > 
> > > >         TODO: Guest Private memory[10] integration - We have been following the
> > > >         series and support will be added once it is merged upstream.
> > > >       ii) Guest support - Support for a Linux Kernel to run in the Realm VM at
> > > >       Realm-EL1, using RSI services. This includes virtio support (virtio-v1.0
> > > >       only). All I/O are treated as non-secure/shared.
> > > >   c) kvmtool - VMM changes required to manage Realm VMs. No guest private memory
> > > >      as mentioned above.
> > > >   d) kvm-unit-tests - Support for running in Realms along with additional tests
> > > >      for RSI ABI.
> > > > 
> > > > Running the stack
> > > > ====================
> > > > 
> > > > To run/test the stack, you would need the following components :
> > > > 
> > > > 1) FVP Base AEM RevC model with FEAT_RME support [4]
> > > > 2) TF-A firmware for EL3 [5]
> > > > 3) TF-A RMM for R-EL2 [3]
> > > > 4) Linux Kernel [6]
> > > > 5) kvmtool [7]
> > > > 6) kvm-unit-tests [8]
> > > > 
> > > > Instructions for building the firmware components and running the model are
> > > > available here [9]. Once, the host kernel is booted, a Realm can be launched by
> > > > invoking the `lkvm` commad as follows:
> > > > 
> > > >   $ lkvm run --realm 				 \
> > > > 	 --measurement-algo=["sha256", "sha512"] \
> > > > 	 --disable-sve				 \
> > > 
> > > As noted above, this is no longer required.
> > > 
> > > > 	 <normal-vm-options>
> > > > 
> > > > Where:
> > > >   * --measurement-algo (Optional) specifies the algorithm selected for creating the
> > > >     initial measurements by the RMM for this Realm (defaults to sha256).
> > > >   * GICv3 is mandatory for the Realms.
> > > >   * SVE is not yet supported in the TF-RMM, and thus must be disabled using
> > > >     --disable-sve
> > > > 
> > > > You may also run the kvm-unit-tests inside the Realm world, using the similar
> > > > options as above.
> > > > 
> > > > 
> > > > Links
> > > > ============
> > > > 
> > > > [0] Arm CCA Landing page (See Key Resources section for various documentations)
> > > >      https://www.arm.com/architecture/security-features/arm-confidential-compute-architecture
> > > > 
> > > > [1] RMM Specification Latest
> > > >      https://developer.arm.com/documentation/den0137/latest
> > > > 
> > > > [2] RMM v1.0-Beta0 specification
> > > >      https://developer.arm.com/documentation/den0137/1-0bet0/
> > > 
> > >   EAC2 spec: https://developer.arm.com/documentation/den0137/1-0eac2/
> > > > 
> > > > [3] Trusted Firmware RMM - TF-RMM
> > > >      https://www.trustedfirmware.org/projects/tf-rmm/
> > > >      GIT: https://git.trustedfirmware.org/TF-RMM/tf-rmm.git
> > > > 
> > > > [4] FVP Base RevC AEM Model (available on x86_64 / Arm64 Linux)
> > > >      https://developer.arm.com/Tools%20and%20Software/Fixed%20Virtual%20Platforms
> > > > 
> > > > [5] Trusted Firmware for A class
> > > >      https://www.trustedfirmware.org/projects/tf-a/ >>>
> > > > [6] Linux kernel support for Arm-CCA
> > > >      https://gitlab.arm.com/linux-arm/linux-cca
> > > >      Host Support branch:	cca-host/rfc-v1
> > > 
> > > Update branch : cca-host/rmm-v1.0-eac2
> > > 
> > > >      Guest Support branch:	cca-guest/rfc-v1
> > > 
> > > Update branch : cca-guest/rmm-v1.0-eac2
> > > 
> > > Combined tree for host and guest is also available at: "cca-full/rmm-v1.0-eac2"
> > > 
> > > > 
> > > > [7] kvmtool support for Arm CCA
> > > >      https://gitlab.arm.com/linux-arm/kvmtool-cca cca/rfc-v1
> > > 
> > > Update branch : cca/rmm-v1.0-eac2
> > > 
> > > > 
> > > > [8] kvm-unit-tests support for Arm CCA
> > > >      https://gitlab.arm.com/linux-arm/kvm-unit-tests-cca  cca/rfc-v1
> > > > 
> > > 
> > > Update branch : cca/rmm-v1.0-eac2
> > > 
> > > 
> > > Suzuki
> > > 
> > > > [9] Instructions for Building Firmware components and running the model, see
> > > >      section 4.19.2 "Building and running TF-A with RME"
> > > >      https://trustedfirmware-a.readthedocs.io/en/latest/components/realm-management-extension.html#building-and-running-tf-a-with-rme
> > > > 
> > > > [10] fd based Guest Private memory for KVM
> > > >     https://lkml.kernel.org/r/20221202061347.1070246-1-chao.p.peng@linux.intel.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Cc: Alexandru Elisei <alexandru.elisei@arm.com>
> > > Cc: Andrew Jones <andrew.jones@linux.dev>
> > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > Cc: Chao Peng <chao.p.peng@linux.intel.com>
> > > Cc: Christoffer Dall <christoffer.dall@arm.com>
> > > Cc: Fuad Tabba <tabba@google.com>
> > > Cc: Jonathan Cameron <jonathan.cameron@huawei.com>
> > > Cc: James Morse <james.morse@arm.com>
> > > Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>
> > > Cc: Joey Gouly <Joey.Gouly@arm.com>
> > > Cc: Marc Zyngier <maz@kernel.org>
> > > Cc: Mark Rutland <mark.rutland@arm.com>
> > > Cc: Oliver Upton <oliver.upton@linux.dev>
> > > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > > Cc: Quentin Perret <qperret@google.com>
> > > Cc: Sean Christopherson <seanjc@google.com>
> > > Cc: Steven Price <steven.price@arm.com>
> > > Cc: Thomas Huth <thuth@redhat.com>
> > > Cc: Will Deacon <will@kernel.org>
> > > Cc: Zenghui Yu <yuzenghui@huawei.com>
> > > To: linux-coco@lists.linux.dev
> > > To: kvmarm@lists.linux.dev
> > > Cc: linux-arm-kernel@lists.infradead.org
> > > To: linux-kernel@vger.kernel.org
> > > To: kvm@vger.kernel.org
> > 
> > Suzuki,
> > Any update to the Arm CCA series (v3?) since last October?
> 
> Yes, we now have a version that supports the final RMM-v1.0
> specification (RMM-v1.0-EAC5). We also have the UEFI EDK2 firmware
> support for Guests in Realm world.
> 
> We are planning to post the changes for review in the v6.8-rc cycle. We
> are trying to integrate the guest_mem support (available in v6.8-rc1) as
> well as reusing some of the arm64 kvm generic interface for configuring
> the Realm parameters (e.g., PMU, SVE_VL etc).
> 
> Here is a version that is missing the items mentioned above, based
> on v6.7-rc4, if anyone would like to try.
> 
> Also, the easiest way to get the components built and model kick started
> is using the shrinkwrap [6] tool, using the cca-3world configuration.
> The tool pulls all the required software components, builds (including
> the buildroot for rootfs) and can run a model using these built
> components.

Hi Suzuki,

This is great news! I've just booted you guys WIP Linux kernel through
shrinkwrap (cca-3world.yaml) without an issue. 
Many thanks to Ryan who delivered an extremely handy tool to us. 

Thanks,
Itaru.

> 
> 
> 
> [0] Linux Repo:
>       Where: git@git.gitlab.arm.com:linux-arm/linux-cca.git
>       KVM Support branch: cca-host/rmm-v1.0-eac5
>       Linux Guest branch: cca-guest/rmm-v1.0-eac5
>       Full stack branch:  cca-full/rmm-v1.0-eac5
> 
> [1] kvmtool Repo:
>       Where: git@git.gitlab.arm.com:linux-arm/kvmtool-cca.git
>       Branch: cca/rmm-v1.0-eac5
> 
> [2] kvm-unit-tests Repo:
>       Where: git@git.gitlab.arm.com:linux-arm/kvm-unit-tests-cca.git
>       Branch: cca/rmm-v1.0-eac5
> 
> [3] UEFI Guest firmware:
>       edk2:     https://git.gitlab.arm.com/linux-arm/edk2-cca.git
>       revision: 2802_arm_cca_rmm-v1.0-eac5
> 
>       edk2-platforms:
> https://git.gitlab.arm.com/linux-arm/edk2-platforms-cca.git
>       revision:       2802_arm_cca_rmm-v1.0-eac5
> 
> 
> [4] RMM Repo:
>       Where: https://git.trustedfirmware.org/TF-RMM/tf-rmm.git
>       tag : tf-rmm-v0.4.0
> 
> [5] TF-A repo:
>       Where: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
>       Tag: v2.10
> 
> 
> [6] https://shrinkwrap.docs.arm.com/en/latest/
>     config: cca-3world.yaml
> 
> Kind regards
> Suzuki
> 
> 

      parent reply	other threads:[~2024-01-12  5:02 UTC|newest]

Thread overview: 190+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 11:22 [RFC] Support for Arm CCA VMs on Linux Suzuki K Poulose
2023-01-27 11:27 ` [RFC PATCH 00/14] arm64: Support for running as a guest in Arm CCA Steven Price
2023-01-27 11:27   ` [RFC PATCH 01/14] arm64: remove redundant 'extern' Steven Price
2023-01-27 11:27   ` [RFC PATCH 02/14] arm64: rsi: Add RSI definitions Steven Price
2023-01-27 11:27   ` [RFC PATCH 03/14] arm64: Detect if in a realm and set RIPAS RAM Steven Price
2023-01-27 11:27   ` [RFC PATCH 04/14] arm64: realm: Query IPA size from the RMM Steven Price
2023-01-27 11:27   ` [RFC PATCH 05/14] arm64: Mark all I/O as non-secure shared Steven Price
2023-01-27 11:27   ` [RFC PATCH 06/14] fixmap: Allow architecture overriding set_fixmap_io Steven Price
2023-01-27 11:27   ` [RFC PATCH 07/14] arm64: Override set_fixmap_io Steven Price
2023-01-27 11:27   ` [RFC PATCH 08/14] arm64: Make the PHYS_MASK_SHIFT dynamic Steven Price
2023-01-27 11:27   ` [RFC PATCH 09/14] arm64: Enforce bounce buffers for realm DMA Steven Price
2023-01-27 11:27   ` [RFC PATCH 10/14] arm64: Enable memory encrypt for Realms Steven Price
2023-01-27 11:27   ` [RFC PATCH 11/14] arm64: Force device mappings to be non-secure shared Steven Price
2023-01-27 11:27   ` [RFC PATCH 12/14] efi: arm64: Map Device with Prot Shared Steven Price
2023-01-27 11:27   ` [RFC PATCH 13/14] arm64: realm: Support nonsecure ITS emulation shared Steven Price
2023-01-27 11:27   ` [RFC PATCH 14/14] HACK: Accept prototype RSI version Steven Price
2023-01-27 11:29 ` [RFC PATCH 00/28] arm64: Support for Arm CCA in KVM Steven Price
2023-01-27 11:29   ` [RFC PATCH 01/28] arm64: RME: Handle Granule Protection Faults (GPFs) Steven Price
2023-01-27 11:29   ` [RFC PATCH 02/28] arm64: RME: Add SMC definitions for calling the RMM Steven Price
2023-01-27 11:29   ` [RFC PATCH 03/28] arm64: RME: Add wrappers for RMI calls Steven Price
2023-02-13 16:43     ` Zhi Wang
2024-03-18  7:03     ` Ganapatrao Kulkarni
2024-03-18 11:22       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 04/28] arm64: RME: Check for RME support at KVM init Steven Price
2023-02-13 15:48     ` Zhi Wang
2023-02-13 15:59       ` Steven Price
2023-03-04 12:07         ` Zhi Wang
2023-02-13 15:55     ` Zhi Wang
2024-03-18  7:17     ` Ganapatrao Kulkarni
2024-03-18 11:22       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 05/28] arm64: RME: Define the user ABI Steven Price
2023-02-13 16:04     ` Zhi Wang
2023-03-01 11:54       ` Steven Price
2023-03-01 20:21         ` Zhi Wang
2023-01-27 11:29   ` [RFC PATCH 06/28] arm64: RME: ioctls to create and configure realms Steven Price
2023-02-07 12:25     ` Jean-Philippe Brucker
2023-02-07 12:55       ` Suzuki K Poulose
2023-02-13 16:10     ` Zhi Wang
2023-03-01 11:55       ` Steven Price
2023-03-01 20:33         ` Zhi Wang
2023-03-06 19:10     ` Zhi Wang
2023-03-10 15:47       ` Steven Price
2024-03-18  7:40     ` Ganapatrao Kulkarni
2024-03-18 11:22       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 07/28] arm64: kvm: Allow passing machine type in KVM creation Steven Price
2023-02-13 16:35     ` Zhi Wang
2023-03-01 11:55       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 08/28] arm64: RME: Keep a spare page delegated to the RMM Steven Price
2023-02-13 16:47     ` Zhi Wang
2023-03-01 11:55       ` Steven Price
2023-03-01 20:50         ` Zhi Wang
2023-01-27 11:29   ` [RFC PATCH 09/28] arm64: RME: RTT handling Steven Price
2023-02-13 17:44     ` Zhi Wang
2023-03-03 14:04       ` Steven Price
2023-03-04 12:32         ` Zhi Wang
2024-03-18 11:01     ` Ganapatrao Kulkarni
2024-03-18 11:25       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 10/28] arm64: RME: Allocate/free RECs to match vCPUs Steven Price
2023-02-13 18:08     ` Zhi Wang
2023-03-03 14:05       ` Steven Price
2023-03-04 12:46         ` Zhi Wang
2023-01-27 11:29   ` [RFC PATCH 11/28] arm64: RME: Support for the VGIC in realms Steven Price
2023-01-27 11:29   ` [RFC PATCH 12/28] KVM: arm64: Support timers in realm RECs Steven Price
2024-03-18 11:28     ` Ganapatrao Kulkarni
2024-03-18 14:14       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 13/28] arm64: RME: Allow VMM to set RIPAS Steven Price
2023-02-17 13:07     ` Zhi Wang
2023-03-03 14:05       ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 14/28] arm64: RME: Handle realm enter/exit Steven Price
2023-01-27 11:29   ` [RFC PATCH 15/28] KVM: arm64: Handle realm MMIO emulation Steven Price
2023-03-06 15:37     ` Zhi Wang
2023-03-10 15:47       ` Steven Price
2023-03-14 15:44         ` Zhi Wang
2023-03-22 11:51           ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 16/28] arm64: RME: Allow populating initial contents Steven Price
2023-03-06 17:34     ` Zhi Wang
2023-03-10 15:47       ` Steven Price
2023-03-14 15:31         ` Zhi Wang
2023-03-22 11:51           ` Steven Price
2023-01-27 11:29   ` [RFC PATCH 17/28] arm64: RME: Runtime faulting of memory Steven Price
2023-03-06 18:20     ` Zhi Wang
2023-03-10 15:47       ` Steven Price
2023-03-14 16:41         ` Zhi Wang
2023-01-27 11:29   ` [RFC PATCH 18/28] KVM: arm64: Handle realm VCPU load Steven Price
2023-01-27 11:29   ` [RFC PATCH 19/28] KVM: arm64: Validate register access for a Realm VM Steven Price
2023-01-27 11:29   ` [RFC PATCH 20/28] KVM: arm64: Handle Realm PSCI requests Steven Price
2023-01-27 11:29   ` [RFC PATCH 21/28] KVM: arm64: WARN on injected undef exceptions Steven Price
2023-01-27 11:29   ` [RFC PATCH 22/28] arm64: Don't expose stolen time for realm guests Steven Price
2023-01-27 11:29   ` [RFC PATCH 23/28] KVM: arm64: Allow activating realms Steven Price
2023-01-27 11:29   ` [RFC PATCH 24/28] arm64: rme: allow userspace to inject aborts Steven Price
2023-01-27 11:29   ` [RFC PATCH 25/28] arm64: rme: support RSI_HOST_CALL Steven Price
2023-01-27 11:29   ` [RFC PATCH 26/28] arm64: rme: Allow checking SVE on VM instance Steven Price
2023-01-27 11:29   ` [RFC PATCH 27/28] arm64: RME: Always use 4k pages for realms Steven Price
2023-01-27 11:29   ` [RFC PATCH 28/28] HACK: Accept prototype RMI versions Steven Price
2023-01-27 11:39 ` [RFC kvmtool 00/31] arm64: Support for Arm Confidential Compute Architecture Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 01/31] arm64: Disable MTE when CFI flash is emulated Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 02/31] script: update_headers: Ignore missing architectures Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 03/31] hw: cfi flash: Handle errors in memory transitions Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 04/31] Add --nocompat option to disable compat warnings Suzuki K Poulose
2023-01-27 12:19     ` Alexandru Elisei
2023-01-27 11:39   ` [RFC kvmtool 05/31] arm64: Check pvtime support against the KVM instance Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 06/31] arm64: Check SVE capability on the VM instance Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 07/31] arm64: Add option to disable SVE Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 08/31] linux: Update kernel headers for RME support Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 09/31] arm64: Add --realm command line option Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 10/31] arm64: Create a realm virtual machine Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 11/31] arm64: Lock realm RAM in memory Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 12/31] arm64: Create Realm Descriptor Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 13/31] arm64: Add --measurement-algo command line option for a realm Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 14/31] arm64: Add configuration step for Realms Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 15/31] arm64: Add support for Realm Personalisation Value Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 16/31] arm64: Add support for specifying the SVE vector length for Realm Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 17/31] arm: Add kernel size to VM context Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 18/31] arm64: Populate initial realm contents Suzuki K Poulose
2023-03-02 14:03     ` Piotr Sawicki
2023-03-02 14:06       ` Suzuki K Poulose
2023-10-02  9:28         ` Piotr Sawicki
2023-01-27 11:39   ` [RFC kvmtool 19/31] arm64: Don't try to set PSTATE for VCPUs belonging to a realm Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 20/31] arm64: Finalize realm VCPU after reset Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 21/31] init: Add last_{init, exit} list macros Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 22/31] arm64: Activate realm before the first VCPU is run Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 23/31] arm64: Specify SMC as the PSCI conduits for realms Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 24/31] arm64: Don't try to debug a realm Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 25/31] arm64: realm: Double the IPA space Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 26/31] virtio: Add a wrapper for get_host_features Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 27/31] virtio: Add arch specific hook for virtio host flags Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 28/31] arm64: realm: Enforce virtio F_ACCESS_PLATFORM flag Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 29/31] mmio: add arch hook for an unhandled MMIO access Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 30/31] arm64: realm: inject an abort on " Suzuki K Poulose
2023-01-27 11:39   ` [RFC kvmtool 31/31] arm64: Allow the user to create a realm Suzuki K Poulose
2023-10-02  9:45   ` [RFC kvmtool 00/31] arm64: Support for Arm Confidential Compute Architecture Piotr Sawicki
2023-01-27 11:40 ` [RFC kvm-unit-tests 00/27] " Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 01/27] lib/string: include stddef.h for size_t Joey Gouly
2023-01-31 14:43     ` Thomas Huth
2023-01-27 11:40   ` [RFC kvm-unit-tests 02/27] arm: Expand SMCCC arguments and return values Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 03/27] arm: realm: Add RSI interface header Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 04/27] arm: Make physical address mask dynamic Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 05/27] arm: Introduce NS_SHARED PTE attribute Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 06/27] arm: Move io_init after vm initialization Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 07/27] arm: realm: Make uart available before MMU is enabled Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 08/27] arm: realm: Realm initialisation Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 09/27] arm: realm: Add support for changing the state of memory Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 10/27] arm: realm: Set RIPAS state for RAM Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 11/27] arm: realm: Early memory setup Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 12/27] arm: realm: Add RSI version test Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 13/27] arm: selftest: realm: skip pabt test when running in a realm Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 14/27] arm: realm: add hvc and RSI_HOST_CALL tests Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 15/27] arm: realm: Add test for FPU/SIMD context save/restore Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 16/27] arm: realm: Add tests for in realm SEA Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 17/27] lib/alloc_page: Add shared page allocation support Joey Gouly
2023-01-27 11:40   ` [RFC kvm-unit-tests 18/27] arm: gic-v3-its: Use shared pages wherever needed Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 19/27] arm: realm: Enable memory encryption Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 20/27] qcbor: Add QCBOR as a submodule Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 21/27] arm: Add build steps for QCBOR library Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 22/27] arm: Add a library to verify tokens using the " Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 23/27] arm: realm: add RSI interface for attestation measurements Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 24/27] arm: realm: Add helpers to decode RSI return codes Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 25/27] arm: realm: Add Realm attestation tests Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 26/27] arm: realm: Add a test for shared memory Joey Gouly
2023-01-27 11:41   ` [RFC kvm-unit-tests 27/27] NOT-FOR-MERGING: add run-realm-tests Joey Gouly
2023-01-27 15:26 ` [RFC] Support for Arm CCA VMs on Linux Jean-Philippe Brucker
2023-02-28 23:35   ` Itaru Kitayama
2023-03-01  9:20     ` Jean-Philippe Brucker
2023-03-01 22:12       ` Itaru Kitayama
2023-03-02  9:18         ` Jean-Philippe Brucker
2023-03-03  9:46         ` Jean-Philippe Brucker
2023-03-03  9:54           ` Suzuki K Poulose
2023-03-03 11:39             ` Jean-Philippe Brucker
2023-03-03 12:08               ` Andrew Jones
2023-03-03 12:19                 ` Suzuki K Poulose
2023-03-03 13:06                   ` Cornelia Huck
2023-03-03 13:57                     ` Jean-Philippe Brucker
2023-02-10 16:51 ` Ryan Roberts
2023-02-10 22:53   ` Itaru Kitayama
2023-02-17  8:02     ` Itaru Kitayama
2023-02-20 10:51       ` Ryan Roberts
2023-02-14 17:13 ` Dr. David Alan Gilbert
2023-03-01  9:58   ` Suzuki K Poulose
2023-03-02 16:46     ` Dr. David Alan Gilbert
2023-03-02 19:02       ` Suzuki K Poulose
2023-07-14 13:46 ` Jonathan Cameron
2023-07-14 15:03   ` Suzuki K Poulose
2023-07-14 16:28     ` Jonathan Cameron
2023-07-17  9:40       ` Suzuki K Poulose
2023-10-02 12:43 ` Suzuki K Poulose
2024-01-10  5:40   ` Itaru Kitayama
2024-01-10 11:41     ` Suzuki K Poulose
2024-01-10 13:44       ` Suzuki K Poulose
2024-01-19  1:26         ` Itaru Kitayama
2024-01-12  5:01       ` Itaru Kitayama [this message]

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=ZaDHu/zUlazt7i+R@vm3 \
    --to=itaru.kitayama@linux.dev \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Ryan.Roberts@arm.com \
    --cc=Sami.Mujawar@arm.com \
    --cc=alexandru.elisei@arm.com \
    --cc=andrew.jones@linux.dev \
    --cc=catalin.marinas@arm.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=christoffer.dall@arm.com \
    --cc=dgilbert@redhat.com \
    --cc=james.morse@arm.com \
    --cc=jean-philippe@linaro.org \
    --cc=joey.gouly@arm.com \
    --cc=jpb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=qperret@google.com \
    --cc=salil.mehta@huawei.com \
    --cc=seanjc@google.com \
    --cc=steven.price@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=thuth@redhat.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.com \
    --cc=zhi.wang.linux@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).