Skip to content

Support execution disablement #154

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

Open
rivos-eblot opened this issue Apr 3, 2025 · 2 comments
Open

Support execution disablement #154

rivos-eblot opened this issue Apr 3, 2025 · 2 comments
Assignees

Comments

@rivos-eblot
Copy link

Some device such as the SRAM controller or the Flash controller may disable instruction fetch while leaving data access.

This needs to be emulated in QEMU.

The most important show stopper for this feature is that the instruction vs. data information is not available outside the vCPU, and forwarding this information down to the devices would require massive QEMU modifications which would hamper any future downstream integrations.

Until this information is available at device level (i.e. in memory APIs), we need to find a ... creative solution.

@rivos-eblot
Copy link
Author

It should be possible to implement execution disablement based on the new ot_vmapper device, which uses the QEMU MMU API and replace the RISC-V MMU with a simplified version that handles address translation and has access to the instruction/data bits.

See #155

@rivos-eblot rivos-eblot removed the ROM label Apr 30, 2025
@rivos-eblot
Copy link
Author

It has been successfully implemented with ot_vmapper. Need to back port this feature from the Darjeeling branch to the current EarlGrey branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant