Repository navigation
virt: add opt-in Aura PV discovery client - #778
Open
DjDeveloperr wants to merge 2 commits into
Open
DjDeveloperr wants to merge 2 commits into
DjDeveloperr wants to merge 2 commits into
Conversation
Contributor
|
Review, not merged yet. It builds in a test merge on integration/aurora 86cb1c3 (with 731 and 856), and the header passes HDRTEST. A few things to fix first:
I'd hold it until the Aura host side lands and one guest run has passed on the Neo. Happy to re-run the build once it's updated. |
Merged
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
CONFIG_AURA_PV) and ABI 0.1 UAPI/dev/aura-pvValidation
drivers/virt/aura_pv.obuilds withCONFIG_AURA_PV=m/dev/aura-pvis unavailable, as expectedThis PR intentionally does not claim
/dev/kvmguest-run, EL1 entry, stage-2 translation, virtual interrupts, timers, or nested guest context switching. The current m1n1 host has one global stage-2/VTTBR context, so a safe per-VM protocol is still required before ABI 0.2 guest execution.