Skip to content

arm64: initial support for CCA in specification and parser#106

Open
jiong-microsoft wants to merge 4 commits intomicrosoft:mainfrom
jiong-microsoft:arm64-cca
Open

arm64: initial support for CCA in specification and parser#106
jiong-microsoft wants to merge 4 commits intomicrosoft:mainfrom
jiong-microsoft:arm64-cca

Conversation

@jiong-microsoft
Copy link

This PR extends 'igvm_def' and 'igvm' crates to support ARM64 CCA.

igvm_def:

  • New IgvmPlatformType::CCA and associated IGVM_CCA_PLATFORM_VERSION.
  • New CcaPolicy to be used with IGVM_VHS_GUEST_POLICY.
  • CCA VpContext follows the convention used by VbsVPContext: a fixed header followed by a list of registers, this gives flexibility on configuring registers' initial value.

igvm:

  • updated a few places to recognize the new CCA platform

Jiong Wang (Arm Ltd) added 2 commits March 3, 2026 09:47
This PR extends 'igvm_def' and 'igvm' crates to support ARM64 CCA.

igvm_def:
  - New IgvmPlatformType::CCA and associated IGVM_CCA_PLATFORM_VERSION.
  - New CcaPolicy to be used with IGVM_VHS_GUEST_POLICY.
  - CCA VpContext follows the convention used by VbsVPContext: a fixed header
    followed by a list of registers, this gives flexibility on configuring
    registers' initial value.

igvm:
  - updated a few places to recognize the new CCA platform

Signed-off-by: Ionut Mihalcea <ionut.mihalcea@arm.com>
Signed-off-by: Jiong Wang <b-jiongwang@microsoft.com>
Use fixed structure type for VPContext
@jiong-microsoft jiong-microsoft requested a review from a team as a code owner March 3, 2026 09:51
@microsoft-github-policy-service

@jiong-microsoft please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Copy link
Member

@chris-oo chris-oo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to have more links to the corresponding ARM specification for each header?

/// reset values.
#[repr(C)]
#[derive(Copy, Clone, Debug, IntoBytes, Immutable, KnownLayout, FromBytes, PartialEq, Eq)]
pub struct IgvmVpContextAArch64Cca {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To confirm, in the CCA spec these are the only registers that can be set and are measured? Is it possible to include a link to the spec in the header definition?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, x0 ~ x7, pc are the only registers contribute to RIM (realm initial measurement), but there is also another 64-bit flags contribute to RIM which we should adds, I will update the PR. The comment will contain links to RMM doc, unfortunately there is permanent doc link, so I can only mention the section number but guess is enough for locating the spec

/// Format of [IGVM_VHS_VP_CONTEXT] file data for a native ARM64 CCA image.
///
/// The VP Context corresponds to the REC (Realm Execution Context) in CCA.
/// Therefore, the fields listed below match those defined in the RMM
/// specification, section "B4.6.69 RmiRecParams type".
///
/// These include the general-purpose registers x0–x7, the PC register,
/// and a 64-bit flags field. All of these fields contribute to the
/// RIM (Realm Initial Measurement).
///
/// One exception is mpidr, which is not included here because it is
/// determined by the host and does not need to be specified in the
/// IGVM file.
///
/// Any registers not explicitly specified here are initialized to their
/// architectural reset values.

pub debug_allowed: u8,
/// Hash algorithm to measure the initial state of the Realm.
#[bits(8)]
pub hash_algorithm: u8,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could this be an open_enum type instead?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch!

pub reserved: u64,
}

/// The Arm CCA policy used in [`IGVM_VHS_GUEST_POLICY::policy`].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are trying to move away from this overloaded guest policy header and back to a single header per-platform for each architectural state. I'll post a PR later today/tomorrow you can see what I think we should do instead.

Jiong Wang (Arm Ltd) added 2 commits March 4, 2026 17:09
  - Add RMM spec section link in comments
  - Add 'flags' in VPContext for Cca to align with RMM REC def
  - Use enum as field types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants