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

PayloadEntry should not assume PcdSystemMemoryUefiRegionSize bytes of memory after the Payload image can be used #4

Open
niruiyu opened this issue Oct 20, 2020 · 1 comment

Comments

@niruiyu
Copy link
Contributor

niruiyu commented Oct 20, 2020

No description provided.

@niruiyu
Copy link
Contributor Author

niruiyu commented Oct 20, 2020

PayloadEntry uses this range of memory to build a new HOB list, based on the information stored in the old HOB list created by boot loader.

I guess the boot loader may creates HOBs in one format but payload expects HOBs in another format. Payload entry is the one that does the HOB convert.

In fact, if the boot loader can directly create the HOBs in final format, payload entry can avoid using the PcdSystemMemoryUefiRegionSize for new HOB creation.

Further checking the implementation, I found PayloadEntry also needs memory to load DXE Core. Anyway, if memory is required by PayloadEntry, better to update the spec to explicitly mention this range.

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

No branches or pull requests

1 participant