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

Dummy ecall circuit #567

Open
1 of 3 tasks
naure opened this issue Nov 6, 2024 · 0 comments · Fixed by #570 or #369
Open
1 of 3 tasks

Dummy ecall circuit #567

naure opened this issue Nov 6, 2024 · 0 comments · Fixed by #570 or #369
Assignees

Comments

@naure
Copy link
Collaborator

naure commented Nov 6, 2024

For some testing scenarios, implement any ecall as NOP instead of trap.

Adding a basic ecall

Usage: Modify VMState.ecall to do whatever is needed. You can also optimize DummyConfig if some operations are not needed.

Adding arbitrary ecalls

  • The current idea is to implement advanced functions in software and call these functions on ECALL as a trap handler.

Safe mode

  • Make sure this cannot be used in production by mistake using some assertion or some compilation feature.
@naure naure self-assigned this Nov 6, 2024
This was referenced Nov 6, 2024
This was linked to pull requests Nov 7, 2024
@naure naure closed this as completed in #369 Nov 8, 2024
@naure naure reopened this Nov 8, 2024
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 a pull request may close this issue.

1 participant