diff options
author | Ard Biesheuvel <[email protected]> | 2019-03-28 20:34:26 +0100 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2019-03-29 07:34:59 +0100 |
commit | c2999c281ea2d2ebbdfce96cecc7b52e2ae7c406 (patch) | |
tree | 49fa5429c8aa361450a517ae138c30e3a376a6ad /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | e8d368ad20f514dce86a64931fe4a6f06a0a6703 (diff) |
efifb: Omit memory map check on legacy boot
Since the following commit:
38ac0287b7f4 ("fbdev/efifb: Honour UEFI memory map attributes when mapping the FB")
efifb_probe() checks its memory range via efi_mem_desc_lookup(),
and this leads to a spurious error message:
EFI_MEMMAP is not enabled
at every boot on KVM. This is quite annoying since the error message
appears even if you set "quiet" boot option.
Since this happens on legacy boot, which strangely enough exposes
a EFI framebuffer via screen_info, let's double check that we are
doing an EFI boot before attempting to access the EFI memory map.
Reported-by: Takashi Iwai <[email protected]>
Tested-by: Takashi Iwai <[email protected]>
Signed-off-by: Ard Biesheuvel <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Matt Fleming <[email protected]>
Cc: Peter Jones <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions