-
-
Notifications
You must be signed in to change notification settings - Fork 170
can't get size of memory_map when it's a failed Result #1539
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
Comments
Hey! Did you actually experience situations where Actually, |
Hi! Yes, I have. Inside of a ExitBootServices hook that's called by winload.efi. What is meant by advanced internal logic? Regardless, thanks for the documentation update! |
Hey, as you can see in #1540, you are not supposed to handle The reason for that is that Does that help? |
Hello! I understand that I do not call/control uefi::boot::memory_map(); winload.efi calls Anyway, as this is something rare, I don't think there's a need to complicate the API - as long as the raw tables continue to be exposed. Thanks for your time and input on this! |
In case the status is Status::BUFFER_TOO_SMALL, map_size should be available. Perhaps through the Error's optional ErrData? Also, memory_map_size is internal, so, the only way seems to be directly using the raw methods in the boot table.
The text was updated successfully, but these errors were encountered: