-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Pci pmem #134
Pci pmem #134
Conversation
@SergiiDmytruk Can you please take a look if you have approached this area as well when rebasing (updating) edk2? |
I remember those patches, but I didn't analyze the code and reasons for them much. As I understand:
If that's correct, then this is an improvement in a sense that things are less broken in this case :) We might want to have this coreboot<->EDK incompatibility tracked somewhere though if it's not already tracked. |
Possibly the same thing caused https://ticket.coreboot.org/issues/415 and https://ticket.coreboot.org/issues/499. In QEMU I initially had it the other way around, |
6fd8282
to
7d04eaa
Compare
This reverts commit 9386264.
Resource allocator used by coreboot may produce intertwined prefetchable and non-prefetchable MMIO regions. Since edk2 assumes that there is at most one continuous region of given type, this may create overlaps. This change removes overlapping part of region from PMem, leaving it only in Mem (and similarly for Above4G variants). By doing so, some of memory regions that could otherwise be WC are now UC, but this is safer than doing it the other way around. The regions are not split into smaller ones, as doing so would lead to bigger fragmentation and potentially depletion of MTRRs. Signed-off-by: Krystian Hebel <krystian.hebel@3mdeb.com>
No description provided.