Skip to content

SNP: Secure AVIC support#1172

Draft
romank-msft wants to merge 1 commit intomicrosoft:mainfrom
romank-msft:savic
Draft

SNP: Secure AVIC support#1172
romank-msft wants to merge 1 commit intomicrosoft:mainfrom
romank-msft:savic

Conversation

@romank-msft
Copy link
Copy Markdown
Contributor

@romank-msft romank-msft commented Apr 10, 2025

Enable secure AVIC support to offload interrupt state computation to the hardware to be fast and secure.

In AMD's own words:

"The Secure AVIC feature provides support for managing guest-owned APIC state for SEV-SNP guests using a private, guest-owned backing page per vCPU."
-- SEV-ES GHCB Standartizarion

"In a virtualized computer system, each guest operating system needs access to an interrupt controller to send and receive device and interprocessor interrupts. When there is no hardware acceleration, it falls to the virtual machine monitor (VMM) to intercept guest-initiated attempts to access the interrupt controller registers and provide direct emulation of the controller system programming interface allowing the guest to initiate and process interrupts. The VMM uses the underlying physical and virtual interrupt delivery mechanisms of the system to deliver interrupts from I/O devices and virtual processors to the target guest virtual processor and to handle any required end of interrupt processing.

Given the high rate of device and interprocessor interrupt generation in certain scenarios, in particular on server-class systems, the emulation of a local APIC can be a significant burden for the VMM. The AVIC architecture addresses the overhead of guest interrupt processing in a virtualized environment by applying hardware acceleration to the following components of interrupt processing:

  • Providing a guest operating system access to performance-critical interrupt controller registers
  • Initiating intra- and inter-processor interrupts (IPIs) in and between virtual processors in a guest"
    -- AMD64 PPR Vol. 3

Laundry list:

  • IGVM parameter for disabling secure AVIC (would someone like that for testing maybe??)
  • Definitions
  • High-level wiring
  • resolve TODOs in the IGVM file generator
  • Auto-enable secure AVIC in the boot shim (from the hw arch pov considered dicey, not doing that)
  • need the secure AVIC kernel patch (comes with kernel 6.12)
  • update the VTL driver to allocate, RMP adjust, and fill out the AVIC backing page,
  • update the kernel interface to map the AVIC page
  • plumbing for (un)registering the backing page in the user mode
  • Implement handling for the non-accelerated AVIC SEV exit
  • Implement handling for the incomplete IPI AVIC SEV exit
  • Make sure INIT and SIPI are delivered
  • Make sure IPIs are delivered
  • Support MpState::Idle and kernel idle and halt state offloading for better performance
  • Fix the existing logic for advancing the RIP (assumes the next RIP is always provided which is true for the automatic exits only, and Windows reads the CCR AVIC register that results in non-AE so the RIP was set to 0 due to next RIP not filled out)
  • Make sure TPR and CR8 are not trashed
  • Fix TMR handling to service level-triggered interrupts reliably
  • Boot multi-proc WIndows
  • Test save/restore, pause/resume, servicing, stress-test

OHCL-Linux-Kernel draft: microsoft/OHCL-Linux-Kernel#67

The change boots multi-proc Linux guests and multi-proc Windows guests.
Sometimes the serial console hangs on MP Linux.

Comment thread vm/loader/manifests/openhcl-x64-cvm-dev.json Outdated
Comment thread vm/x86/x86defs/src/snp.rs
Comment thread openhcl/hcl/src/protocol.rs Outdated
Comment thread openhcl/hcl/src/ioctl.rs
Comment thread openhcl/hcl/src/protocol.rs Outdated
Comment thread vm/loader/src/importer.rs Outdated
Comment thread openhcl/hcl/src/ioctl.rs Outdated
Comment thread openhcl/hcl/src/ioctl.rs
Comment thread openhcl/openhcl_boot/src/host_params/shim_params.rs Outdated
Comment thread openhcl/openhcl_boot/src/arch/x86_64/snp.rs Outdated
Comment thread openhcl/openhcl_boot/src/arch/x86_64/snp.rs Outdated
@romank-msft romank-msft force-pushed the savic branch 4 times, most recently from c2a6131 to 29dc5e4 Compare April 23, 2025 19:14
Comment thread vm/hv1/hvdef/src/lib.rs
@romank-msft romank-msft force-pushed the savic branch 2 times, most recently from da9191e to 082bdc5 Compare April 30, 2025 19:37
@romank-msft romank-msft force-pushed the savic branch 5 times, most recently from 86af935 to 3687496 Compare May 8, 2025 21:59
@romank-msft romank-msft force-pushed the savic branch 2 times, most recently from aabca2d to 074cb5d Compare May 10, 2025 16:34
Comment thread openhcl/hcl/src/ioctl.rs Outdated
"enable_debug": true,
"injection_type": "normal"
"injection_type": "normal",
"secure_avic": "enabled"
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

revert to "disabled"

@romank-msft romank-msft force-pushed the savic branch 2 times, most recently from a17bbe0 to 4ead4cf Compare May 10, 2025 20:27
@romank-msft romank-msft force-pushed the savic branch 3 times, most recently from 91e198d to 3ab9286 Compare May 15, 2025 17:16
@romank-msft romank-msft force-pushed the savic branch 4 times, most recently from 5ab32f2 to 3472a20 Compare May 30, 2025 21:54
@romank-msft romank-msft force-pushed the savic branch 3 times, most recently from ab868e9 to 925a258 Compare June 11, 2025 21:49
@romank-msft romank-msft force-pushed the savic branch 2 times, most recently from a4010a8 to f0d8c97 Compare June 17, 2025 00:14
@romank-msft romank-msft force-pushed the savic branch 7 times, most recently from eb422e9 to accd50e Compare July 1, 2025 18:23
@romank-msft romank-msft force-pushed the savic branch 2 times, most recently from 97a3e29 to 8f521a1 Compare September 3, 2025 22:49
@romank-msft romank-msft force-pushed the savic branch 3 times, most recently from e21d18b to ce710cc Compare September 30, 2025 21:42
@benhillis
Copy link
Copy Markdown
Member

Hi! 👋 We're doing some spring cleaning on open PRs. This PR hasn't seen any activity in a while — is it still something you're working on or planning to pick back up? No worries either way! If it's no longer needed, we'll go ahead and close it out. Just let us know. Thanks!

@microsoft-github-policy-service
Copy link
Copy Markdown

@romank-msft 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.

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.

7 participants