Skip to content

L4 inaccessible without bootloader provided virtual offset #513

Description

@DuncanMcPherson

I have spent pretty close to a week trying to figure this out. In older versions there was the map_physical_memory feature, which appears to have been removed as of v0.10.0. I have tried everything I can think of to no avail. Any time I try to access the L4 table to map the rest of the memory, I get a page daily.

Things I have tried:

  • reverse calculating an offset from the logs
  • creating a new L4 using 4KiB aligned static mut
  • I even tried patching in an offset on my own fork of the repo

I am at a loss for how to set up memory without a valid offset

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions