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

Create memory map documentation #89

Open
Vild opened this issue Jun 21, 2018 · 0 comments
Open

Create memory map documentation #89

Vild opened this issue Jun 21, 2018 · 0 comments
Labels
effort: low The issue will probably take a single contributor no more than one day of work to resolve. priority: low The issue has only a small impact on people using the software. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation.
Milestone

Comments

@Vild
Copy link
Member

Vild commented Jun 21, 2018

Create something that shows the following information:

  • What is between two virtual address?
  • Maybe, How can read it?
  • What code is using it? ie. What files uses it.
  • Is it mapped to a specific physical address?
    • If yes, what is special about this physical address?
  • Is it permanently mapped or just for a while?

And probably some more good information

Currently:
[0][0][0][184] - VGA
[0][0][0][256] - Loader
[255] - Userspace stacks
[500] - Kernel Heap
[509] - Recursive mapping
[510][0][0] - "Special" mapping (temporary mapping)
[510][0][1][0] - LAPIC
[510][0][2-18] - 32Mebi of initrd space.
[510][1] - AP stacks, 16 pages per AP. 128 Kibicores in total 🥇
[511] - Kernel code

@Vild Vild added effort: low The issue will probably take a single contributor no more than one day of work to resolve. priority: low The issue has only a small impact on people using the software. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation. labels Jun 21, 2018
@Vild Vild added this to the Version 0.3 milestone Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: low The issue will probably take a single contributor no more than one day of work to resolve. priority: low The issue has only a small impact on people using the software. type: documentation This issue pertains to the clarity or exhaustiveness of package documentation.
Projects
PowerNex Kernel
  
Awaiting triage
Development

No branches or pull requests

1 participant