Skip to content
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

small fixes #530

Merged
merged 1 commit into from
Feb 10, 2025
Merged

small fixes #530

merged 1 commit into from
Feb 10, 2025

Conversation

tariqkurd-repo
Copy link
Collaborator

No description provided.

@arichardson arichardson merged commit 3783bb8 into riscv:main Feb 10, 2025
3 checks passed
@@ -26,14 +26,14 @@ privileged architecture specified in the RISC-V ISA.
=== Memory

A hart supporting {cheri_base_ext_name} has a single byte-addressable address
space of 2^XLEN^ bytes for all memory accesses. Each memory region capable of
space of 2^MXLEN^ bytes for all memory accesses. Each memory region capable of
Copy link
Collaborator

@andresag01 andresag01 Feb 11, 2025

Choose a reason for hiding this comment

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

@tariqkurd-repo @arichardson : This was correct and it was taken directly from the RISC-V unprivileged specification where it says (see Page 16 Section 1.4 here):

A RISC-V hart has a single byte-addressable address space of 2^XLEN^ bytes for all memory accesses.

It is meant to be the effective XLEN of the machine which can be MXLEN or SXLEN or UXLEN depending CSRs. The idea is that the byte-addressable memory space is just like in CHERI-less RISC-V so we are fully compatible, but capability bounds remain encoded in MXLEN width regardless of the effective XLEN.

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.

3 participants