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

Interface: Memory allocation #44

Open
Qix- opened this issue Jan 18, 2025 · 0 comments
Open

Interface: Memory allocation #44

Qix- opened this issue Jan 18, 2025 · 0 comments
Labels
interfaces Relates to interfaces provided by the kernel

Comments

@Qix-
Copy link
Member

Qix- commented Jan 18, 2025

The memory allocation interface(s) allow the allocation of physical pages at runtime, as well as for the management of memory mappings in the instance's / thread's address space.

These are particularly sensitive to design given a few considerations:

  • Port buffers must work with these
  • "Priority" allocations, such as DMA memory regions
  • Physical allocation checks during mapping
  • Avoiding exposing direct paddrs to the userspace processes (security concern)

Further, given the kernel avoids working with any linear data (except in the case of ports) much of this must be performed in "constant space" via the ABI.

@Qix- Qix- added the interfaces Relates to interfaces provided by the kernel label Jan 18, 2025
@Qix- Qix- added this to the v0 (killswitch) milestone Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interfaces Relates to interfaces provided by the kernel
Development

No branches or pull requests

1 participant