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

Add base address register as extra argument to ext_data_check_addr hook #5

Merged
merged 2 commits into from
May 2, 2019

Conversation

rmn30
Copy link
Collaborator

@rmn30 rmn30 commented May 1, 2019

This will assist with implementing CHERI capability mode.

…ok to assist with implementing CHERI capability mode.
@rmn30 rmn30 requested a review from pmundkur May 1, 2019 16:20
@rmn30
Copy link
Collaborator Author

rmn30 commented May 1, 2019

In the CHERI case for LOAD and STORE we end up reading rs1 twice which is unfortunate and could be a problem with RMEM. We could avoid this by moving the read and add into the handler in both cases and just passing in the offset, but it might be slightly confusing to read in the vanilla RISCV model. If it helps we could rename the hook compute_memory_addr or something.

@pmundkur
Copy link
Contributor

pmundkur commented May 2, 2019

Moving the read and add into the handler looks preferable. We need to document the hook anyway, and we could perhaps add an additional clarifying comment in the vanilla model. would data_get_addr be okay as a name? i.e. just changing check -> get.

…t to data_get_addr. This avoids a double register read in CHERI case.
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.

2 participants