Scott has reported another bug in the EFI mapping code which caused
page faults during SetVirtualAddressMap() because we're using 1GB
pages at the PUD level even though they may not be supported by the
cpu.
This patch is against tip/efi/core even though the bug has existed
since populate_pud() was first written in 2013. The reason I didn't
base it on tip/x86/urgent is because it would generate conflicts when
the stuff in tip/efi/core gets merged and since no one has ever
reported hitting it until now.
Let me know if you'd like me to respin this patch on top of something
else.
The following changes since commit 2ad510dc372c2caac9aada9ff6dd10e787616e1d:
x86/efi: Only map kernel text for EFI mixed mode (2016-02-22 08:26:28 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent
for you to fetch changes up to a239b3605abff1457005b413047ddeef057a0831:
x86/mm/pat: Fix boot crash when 1GB pages are not supported by cpu (2016-03-14 10:13:05 +0000)
----------------------------------------------------------------
* We currently always assume that 1GB PUD pages are supported by the
cpu which has resulted in reports of boot crashes (PF_RSVD faults)
during SetVirtualAddressMap() when that assumption turns out to be
false. Only use 1GB pages if supported by the cpu - Matt Fleming
----------------------------------------------------------------
Matt Fleming (1):
x86/mm/pat: Fix boot crash when 1GB pages are not supported by cpu
arch/x86/mm/pageattr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
