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

Should ReservedMemExecutable be set to 0 or 1? #495

Open
bvavala opened this issue Jun 17, 2024 · 0 comments
Open

Should ReservedMemExecutable be set to 0 or 1? #495

bvavala opened this issue Jun 17, 2024 · 0 comments

Comments

@bvavala
Copy link
Member

bvavala commented Jun 17, 2024

The WAMR interpreter requires ReservedMem inside the enclave for its operations -- see WAMR and the ReservedMemExecutable field in the eservice enclave xml file.
If AoT or jitted code is used, then the memory has to be executable. Otherwise, that is not necessary.
With that said, is it ok to leave the ReservedMemExecutable field set to 1, or should it be set to 0?

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

1 participant