-
Notifications
You must be signed in to change notification settings - Fork 59
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
Improved EFI support towards Windows guest #114
Improved EFI support towards Windows guest #114
Conversation
Signed-off-by: Akira Moroo <[email protected]>
The Windows bootloader seems to use the function to calibrate the clock and timer. Signed-off-by: Akira Moroo <[email protected]>
Signed-off-by: Akira Moroo <[email protected]>
As per UEFI Specification 2.8[1] section 2.3.4, the stack space is 128 KiB or more for x64. [1] https://uefi.org/sites/default/files/resources/UEFI%20Spec%202.8B%20May%202020.pdf Signed-off-by: Akira Moroo <[email protected]>
This is a workaround for Windows10 20H2 BSoD. Signed-off-by: Akira Moroo <[email protected]>
The "fat" LTO causes stuck on Windows 10 20H2 boot with release build. Signed-off-by: Akira Moroo <[email protected]>
The workaround introduced in ff50324 causes kernel panic on the recent Linux kernel during calling RuntimeServices.set_virtual_address_map. This is because the region reported as RuntimeServicesData type is actually text section which seems to be mapped to non-executable pages. In this commit, it registers the text section as RuntimeServicesCode and the other firmware regions are reported as RuntimeServicesData. Signed-off-by: Akira Moroo <[email protected]>
@retrage After your last commit I have to admit I didn't retest Windows. Did it work for you? I get the following error:
Going back to 282ebc0 makes Windows boot fine. So I think there needs to be a little bit more refinement on the memory map. |
@rbradford I got a different error, and the previous commit 282ebc0 works too.
I had to run regression tests before pushing them... |
This is the subset of patches from #110 without the integration tests for Windows. I would like to merge these and then make a new release here and use that in CH's upcoming release. However the Windows integration tests here need a fix that is not yet in a released CH.