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

API for dealing with cache-coherency on ARM #115

Open
Ivan-Velickovic opened this issue Mar 26, 2024 · 1 comment
Open

API for dealing with cache-coherency on ARM #115

Ivan-Velickovic opened this issue Mar 26, 2024 · 1 comment

Comments

@Ivan-Velickovic
Copy link
Collaborator

Ivan-Velickovic commented Mar 26, 2024

There is currently no API for doing cache operations on ARM platforms. This leads to code like this

seL4_ARM_VSpace_CleanInvalidate_Data(3, (uintptr_t)packet, ((uintptr_t)packet) + length);

which should not be necessary.

We could add simple wrappers such as microkit_arm_cache_clean and microkit_arm_cache_invalidate and so on, these would simply abstract away the VSpace cap since it's fixed.

However, I believe the default seL4 configurations for AArch64 also allow users to do some of these operations from user-space. Should these microkit_arm_cache_* APIs only call the system call if caching operations from user-space are not enabled? Are there any issues with this indirection? Should we be simple and only supply the system call wrappers and leave it to users to decide what to do?

It certainly leads to better performance.

@gernotheiser
Copy link
Member

We should definitely not force system calls for things that can be done in usermode.

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