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

LOWEST_VADDR_CURR_PRIV/HIGHEST_VADDR_CURR_PRIV #8

Open
janhoogerbrugge-nxp opened this issue Dec 10, 2024 · 1 comment
Open

LOWEST_VADDR_CURR_PRIV/HIGHEST_VADDR_CURR_PRIV #8

janhoogerbrugge-nxp opened this issue Dec 10, 2024 · 1 comment

Comments

@janhoogerbrugge-nxp
Copy link

I was wondering where these values are coming from:

LOWEST_VADDR_CURR_PRIV: Lowest virtual address in current privilege.
HIGHEST_VADDR_CURR_PRIV: Highest virtual address in current privilege.

Are these values 0 and 2^64-1 or something else? If something else, how does the core get them?

Jan.

@deepak0414
Copy link
Collaborator

Sorry for being late on this.

Since memory tagging is 64 bit only feature.
Planning to make a dependency of Svatag on Svukte (riscv/riscv-isa-manual#1564)

Svukte makes it implicit that user and supervisor are split half evenly.

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

No branches or pull requests

2 participants