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

[patch-axel-24] init_freemem() with phys addresses #100

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

axel-h
Copy link
Owner

@axel-h axel-h commented May 15, 2023

No description provided.

- Adjust free memory to kernel window, as well for the lower as the
upper limit.
- Log more detailed boot message to help porting.

Signed-off-by: Axel Heider <[email protected]>
Signed-off-by: Axel Heider <[email protected]>
Handling memory based on physical addresses during boot is more
intuitive and issues are easier to debug. This also requires much fewer
conversions between region_t and p_region_t.

Signed-off-by: Axel Heider <[email protected]>
Handling memory based on physical addresses during boot is more
intuitive and issues are easier to debug. This also requires much fewer
conversions between region_t and p_region_t.

Signed-off-by: Axel Heider <[email protected]>
Creating the untypeds is the place in the boot process where the switch
from plain physical addresses to addressing physical memory via the
kernel window happens. Passing physical region creates a single place of
control, to check what can be addressed and what not.
The region (or a part of) it could be outside the kernel window, so it
cannot be accessed. Ensure to never generate a pptr outside of that
window.

Signed-off-by: Axel Heider <[email protected]>
- pass phys regions to arch_init_freemem()
- make reserve_region() publicly available, make it smarter to insert or
  merge new regions, make it take physical regions.
- remove 'reserved' and 'resv_count' from 'ndks_boot_t' and declare it a
  internal variable of the generic boot code.

Signed-off-by: Axel Heider <[email protected]>
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 this pull request may close these issues.

1 participant