Skip to content

Clarify how mhselect[2] is concatenated with mhvalue #1139

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify how mhselect[2] is concatenated with mhvalue #1139

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions xml/hwbp_registers.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1445,11 +1445,15 @@ same project unless stated otherwise.

1, 5 (mcontext_select): This trigger will only match or fire if the
low bits of
{csr-mcontext}/{csr-hcontext} equal {{textra32-mhvalue}, mhselect[2]}.
{csr-mcontext}/{csr-hcontext} equal
a concatenation of {textra32-mhvalue} and {mhselect[2]} with
{mhselect[2]} as the least significant bit.

2, 6 (vmid_select): This trigger will only match or fire if VMID in
hgatp equals the lower VMIDMAX
(defined in the Privileged Spec) bits of {{textra32-mhvalue}, mhselect[2]}.
{hgatp} equals the lower VMIDMAX
(defined in the Privileged Spec) bits of
a concatenation of {textra32-mhvalue} and {mhselect[2]} with
{mhselect[2]} as the least significant bit.

3, 7 (reserved): Reserved.

Expand Down