Skip to content

make MemoryMap own its buffer (Vec) #1204

Closed
@DaniD3v

Description

@DaniD3v

To save your system Memory Map you need to call boot_services.memory_map_size() and allocate. I don't think doing this is possible without heap allocations? If that's the case why not just make MemoryMap own a vector, make memory_map_size() private (to increase usability) and remove the lifetime on MemoryMap?

I don't think there would be any downsides to doing that. I don't have a lot of experience in either UEFI or OSdev so feel free to correct me if I'm wrong

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