On Sat, 19 Dec, at 03:45:51PM, Josh Triplett wrote: > On Sat, Dec 19, 2015 at 12:28:41PM -0800, tip-bot for Sai Praneeth wrote: > > As said above one way to fix this bug is to shift %cr3 to efi_pgd but we > > are not doing that way because it leaks inner details of how we switch > > to EFI page tables into a new call site and it also adds duplicate code. > > Instead, we remove the call to efi_lookup_mapped_addr() and always > > perform early_mem*() instead of early_io*() because we want to remap RAM > > regions and not I/O regions. We also delete efi_lookup_mapped_addr() > > because we are no longer using it. > > Did the follow-up fix commit from the thread "BGRT doesn't work for me > on efi-next", fixing the WARN reported by Môshe van der Sterre, get > pulled in? Because this commit still uses early_memremap, not memremap. No it didn't. I'm going to send it to tip in a minute. -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|