Skip to content

openhcl/openhcl_dma_manager: disallow lower vtl hypercall on hardware isolated platforms #1542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 18, 2025

Conversation

chris-oo
Copy link
Member

This hypercall should not be used on hardware isolated platforms, as the hypervisor is untrusted. It shouldn't be used already today, but enforce it.

@chris-oo chris-oo requested a review from a team as a code owner June 18, 2025 19:48
@chris-oo chris-oo added the backport_2505 Change should be backported to the release/2505 branch label Jun 18, 2025
sluck-msft
sluck-msft previously approved these changes Jun 18, 2025
Co-authored-by: Steven Malis <smmalis37@gmail.com>
@chris-oo chris-oo enabled auto-merge (squash) June 18, 2025 21:23
@chris-oo chris-oo merged commit f3d183f into microsoft:main Jun 18, 2025
28 checks passed
@chris-oo chris-oo deleted the no-vtl-lower-hypercall branch June 18, 2025 21:54
chris-oo added a commit to chris-oo/openvmm that referenced this pull request Jun 19, 2025
… isolated platforms (microsoft#1542)

This hypercall should not be used on hardware isolated platforms, as the
hypervisor is untrusted. It shouldn't be used already today, but enforce
it.

---------

Co-authored-by: Steven Malis <smmalis37@gmail.com>
chris-oo added a commit that referenced this pull request Jun 21, 2025
… isolated platforms (#1542) (#1549)

This hypercall should not be used on hardware isolated platforms, as the
hypervisor is untrusted. It shouldn't be used already today, but enforce
it.

Cherry pick of (#1542)

Co-authored-by: Steven Malis <smmalis37@gmail.com>
@benhillis
Copy link
Member

Backported in #1549

@benhillis benhillis added backported_2505 PR that has been backported to release/2505 and removed backport_2505 Change should be backported to the release/2505 branch labels Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported_2505 PR that has been backported to release/2505
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants