RISC-V Vector Extension Support#351
Open
ninolomata wants to merge 1 commit into
Open
Conversation
Signed-off-by: Bruno Sa <bruno.vilaca.sa@gmail.com>
ninolomata
requested review from
DavidMCerdeira,
danielRep,
josecm,
malejo97,
miguelafsilva5 and
sandro2pinto
as code owners
danielRep
approved these changes
May 18, 2026
Member
danielRep
left a comment
danielRep
left a comment
There was a problem hiding this comment.
LGTM. Spec for anyone reviewing too. https://docs.riscv.org/reference/isa/extensions/vector/_attachments/riscv-v-spec.pdf
Can you rebase @ninolomata ?
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
2 participants
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.
Adds optional support for exposing the RISC-V vector extension to guests.
This change:
sstatus.VSfield definitionsVS=Dirtyin both
sstatusandvsstatusCPU_EXT_Vplatform configuration macro to control vector extension exposure.