Changes in Makefile

37aee82c - x86/efi: Drop support for fake EFI memory maps

Thu, 20 Jun 2024 07:10:49 +0000

x86/efi: Drop support for fake EFI memory mapsBetween kexec and confidential VM support, handling the EFI memory mapscorrectly on x86 is already proving to be rather difficult (as opposedto other EFI architectures which manage to never modify the EFI memorymap to begin with)EFI fake memory map support is essentially a development hack (fortesting new support for the 'special purpose' and 'more reliable' EFImemory attributes) that leaked into production code. The regions markedin this manner are not actually recognized as such by the firmwareitself or the EFI stub (and never have), and marking memory as 'morereliable' seems rather futile if the underlying memory is just ordinaryRAM.Marking memory as 'special purpose' in this way is also dubious, but maybe in use in production code nonetheless. However, the same should beachievable by using the memmap= command line option with the ! operator.EFI fake memmap support is not enabled by any of the major distros(Debian, Fedora, SUSE, Ubuntu) and does not exist on otherarchitectures, so let's drop support for it.Acked-by: Borislav Petkov (AMD) Acked-by: Dan Williams Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/arch/x86/platform/efi/Makefile

1fff234d - efi: x86: Move EFI runtime map sysfs code to arch/x86

Mon, 07 Nov 2022 08:17:16 +0000

efi: x86: Move EFI runtime map sysfs code to arch/x86The EFI runtime map code is only wired up on x86, which is the onlyarchitecture that has a need for it in its implementation of kexec.So let's move this code under arch/x86 and drop all references to itfrom generic code. To ensure that the efi_runtime_map_init() is invokedat the appropriate time use a 'sync' subsys_initcall() that will becalled right after the EFI initcall made from generic code where theoriginal invocation of efi_runtime_map_init() resided.Signed-off-by: Ard Biesheuvel Reviewed-by: Dave Young List of files: /linux-6.15/arch/x86/platform/efi/Makefile

fdc6d38d - efi: memmap: Move manipulation routines into x86 arch tree

Sat, 01 Oct 2022 17:09:24 +0000

efi: memmap: Move manipulation routines into x86 arch treeThe EFI memory map is a description of the memory layout as provided bythe firmware, and only x86 manipulates it in various different ways forits own memory bookkeeping. So let's move the memmap routines that areonly used by x86 into the x86 arch tree.Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/arch/x86/platform/efi/Makefile

4059ba65 - efi: memmap: Move EFI fake memmap support into x86 arch tree

Sat, 01 Oct 2022 16:38:15 +0000

efi: memmap: Move EFI fake memmap support into x86 arch treeThe EFI fake memmap support is specific to x86, which manipulates theEFI memory map in various different ways after receiving it from the EFIstub. On other architectures, we have managed to push back on this, andthe EFI memory map is kept pristine.So let's move the fake memmap code into the x86 arch tree, where itarguably belongs.Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/arch/x86/platform/efi/Makefile

537da1ed - objtool,efi: Update __efi64_thunk annotation

Tue, 08 Mar 2022 15:30:15 +0000

objtool,efi: Update __efi64_thunk annotationThe current annotation relies on not running objtool on the file; thiswon't work when running objtool on vmlinux.o. Instead explicitly mark__efi64_thunk() to be ignored.This preserves the status quo, which is somewhat unfortunate. Luckilythis code is hardly ever used.Signed-off-by: Peter Zijlstra (Intel) Acked-by: Josh Poimboeuf Link: https://lore.kernel.org/r/20220308154317.402118218@infradead.org List of files: /linux-6.15/arch/x86/platform/efi/Makefile

ac6119e7 - efi/x86: Disable instrumentation in the EFI runtime handling code

Tue, 21 Jan 2020 09:39:12 +0000

efi/x86: Disable instrumentation in the EFI runtime handling codeWe already disable KASAN instrumentation specifically for theEFI routines that are known to dereference memory addresses thatKASAN does not know about, avoiding false positive KASAN splats.However, as it turns out, having GCOV or KASAN instrumentation enabledinterferes with the compiler's ability to optimize away function callsthat are guarded by IS_ENABLED() checks that should have resulted inthose references to have been const-propagated out of existence. Butwith instrumenation enabled, we may get build errors like: ld: arch/x86/platform/efi/efi_64.o: in function `efi_thunk_set_virtual_address_map': ld: arch/x86/platform/efi/efi_64.o: in function `efi_set_virtual_address_map':in builds where CONFIG_EFI=y but CONFIG_EFI_MIXED or CONFIG_X86_UV are notdefined, even though the invocations are conditional on IS_ENABLED() checksagainst the respective Kconfig symbols.So let's disable instrumentation entirely for this subdirectory, whichisn't that useful here to begin with.Signed-off-by: Ard Biesheuvel Signed-off-by: Ingo Molnar Cc: linux-efi@vger.kernel.org List of files: /linux-6.15/arch/x86/platform/efi/Makefile

e5f930fe - efi/x86: Simplify 64-bit EFI firmware call wrapper

Fri, 03 Jan 2020 11:39:42 +0000

efi/x86: Simplify 64-bit EFI firmware call wrapperThe efi_call() wrapper used to invoke EFI runtime services servesa number of purposes:- realign the stack to 16 bytes- preserve FP and CR0 register state- translate from SysV to MS calling convention.Preserving CR0.TS is no longer necessary in Linux, and preserving theFP register state is also redundant in most cases, since efi_call() isalmost always used from within the scope of a pair of kernel_fpu_begin()/kernel_fpu_end() calls, with the exception of the early call toSetVirtualAddressMap() and the SGI UV support code.So let's add a pair of kernel_fpu_begin()/_end() calls there as well,and remove the unnecessary code from the assembly implementation ofefi_call(), and only keep the pieces that deal with the stackalignment and the ABI translation.Signed-off-by: Ard Biesheuvel Cc: Andy Lutomirski Cc: Ard Biesheuvel Cc: Arvind Sankar Cc: Matthew Garrett Cc: linux-efi@vger.kernel.orgLink: https://lkml.kernel.org/r/20200103113953.9571-10-ardb@kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/efi/Makefile

69c1f396 - efi/x86: Convert x86 EFI earlyprintk into generic earlycon implementation

Sat, 02 Feb 2019 09:41:18 +0000

efi/x86: Convert x86 EFI earlyprintk into generic earlycon implementationMove the x86 EFI earlyprintk implementation to a shared location underdrivers/firmware and tweak it slightly so we can expose it as an earlyconimplementation (which is generic) rather than earlyprintk (which is onlyimplemented for a few architectures)This also involves switching to write-combine mappings by default (whichis required on ARM since device mappings lack memory semantics, and somemcpy/memset may not be used on them), and adding support for sharedmemory framebuffers on cache coherent non-x86 systems (which do nottolerate mismatched attributes).Note that 32-bit ARM does not populate its struct screen_info earlyenough for earlycon=efifb to work, so it is disabled there.Signed-off-by: Ard Biesheuvel Reviewed-by: Alexander Graf Cc: AKASHI Takahiro Cc: Bjorn Andersson Cc: Borislav Petkov Cc: Heinrich Schuchardt Cc: Jeffrey Hugo Cc: Lee Jones Cc: Leif Lindholm Cc: Linus Torvalds Cc: Matt Fleming Cc: Peter Jones Cc: Peter Zijlstra Cc: Sai Praneeth Prakhya Cc: Thomas Gleixner Cc: linux-efi@vger.kernel.orgLink: http://lkml.kernel.org/r/20190202094119.13230-10-ard.biesheuvel@linaro.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/efi/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/x86/platform/efi/Makefile

c207aee4 - objtool, x86: Add several functions and files to the objtool whitelist

Wed, 28 Jun 2017 15:11:06 +0000

objtool, x86: Add several functions and files to the objtool whitelistIn preparation for an objtool rewrite which will have broader checks,whitelist functions and files which cause problems because they dounusual things with the stack.These whitelists serve as a TODO list for which functions and filesdon't yet have undwarf unwinder coverage. Eventually most of thewhitelists can be removed in favor of manual CFI hint annotations orobjtool improvements.Signed-off-by: Josh Poimboeuf Cc: Andy Lutomirski Cc: Jiri Slaby Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: live-patching@vger.kernel.orgLink: http://lkml.kernel.org/r/7f934a5d707a574bda33ea282e9478e627fb1829.1498659915.git.jpoimboe@redhat.comSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/efi/Makefile

75def552 - x86/efi/bgrt: Move efi-bgrt handling out of arch/x86

Tue, 04 Apr 2017 16:02:40 +0000

x86/efi/bgrt: Move efi-bgrt handling out of arch/x86Now with open-source boot firmware (EDK2) supporting ACPI BGRT tableaddition even for architectures like AARCH64, it makes sense to moveout the 'efi-bgrt.c' file and supporting infrastructure from 'arch/x86'directory and house it inside 'drivers/firmware/efi', so that this commoncode can be used across architectures.Signed-off-by: Bhupesh Sharma Signed-off-by: Ard Biesheuvel Cc: Linus Torvalds Cc: Matt Fleming Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: linux-efi@vger.kernel.orgLink: http://lkml.kernel.org/r/20170404160245.27812-7-ard.biesheuvel@linaro.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/efi/Makefile

c0dd6716 - objtool: Mark non-standard object files and directories

Mon, 29 Feb 2016 04:22:34 +0000

objtool: Mark non-standard object files and directoriesCode which runs outside the kernel's normal mode of operation often doesunusual things which can cause a static analysis tool like objtool toemit false positive warnings: - boot image - vdso image - relocation - realmode - efi - head - purgatory - modpostSet OBJECT_FILES_NON_STANDARD for their related files and directories,which will tell objtool to skip checking them. It's ok to skip thembecause they don't affect runtime stack traces.Also skip the following code which does the right thing with respect toframe pointers, but is too "special" to be validated by a tool: - entry - mcountAlso skip the test_nx module because it modifies its exception handlingtable at runtime, which objtool can't understand. Fortunately it'sjust a test module so it doesn't matter much.Currently objtool is the only user of OBJECT_FILES_NON_STANDARD, but itmight eventually be useful for other tools.Signed-off-by: Josh Poimboeuf Cc: Andrew Morton Cc: Andy Lutomirski Cc: Arnaldo Carvalho de Melo Cc: Bernd Petrovitsch Cc: Borislav Petkov Cc: Chris J Arges Cc: Jiri Slaby Cc: Linus Torvalds Cc: Michal Marek Cc: Namhyung Kim Cc: Pedro Alves Cc: Peter Zijlstra Cc: Thomas Gleixner Cc: live-patching@vger.kernel.orgLink: http://lkml.kernel.org/r/366c080e3844e8a5b6a0327dc7e8c2b90ca3baeb.1456719558.git.jpoimboe@redhat.comSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/platform/efi/Makefile

eeb9db09 - x86/efi: Move all workarounds to a separate file quirks.c

Mon, 02 Jun 2014 12:18:35 +0000

x86/efi: Move all workarounds to a separate file quirks.cCurrently, it's difficult to find all the workarounds that areapplied when running on EFI, because they're littered throughoutvarious code paths. This change moves all of them into a separatefile with the hope that it will be come the single location for allour well documented quirks.Signed-off-by: Saurabh Tangri Signed-off-by: Matt Fleming List of files: /linux-6.15/arch/x86/platform/efi/Makefile

4f9dbcfc - x86/efi: Add mixed runtime services support

Fri, 10 Jan 2014 18:48:30 +0000

x86/efi: Add mixed runtime services supportSetup the runtime services based on whether we're booting in EFI nativemode or not. For non-native mode we need to thunk from 64-bit into32-bit mode before invoking the EFI runtime services.Using the runtime services after SetVirtualAddressMap() is slightly morecomplicated because we need to ensure that all the addresses we pass tothe firmware are below the 4GB boundary so that they can be addressedwith 32-bit pointers, see efi_setup_page_tables().Signed-off-by: Matt Fleming List of files: /linux-6.15/arch/x86/platform/efi/Makefile

72548e83 - x86/efi: Add EFI framebuffer earlyprintk support

Fri, 04 Oct 2013 08:36:56 +0000

x86/efi: Add EFI framebuffer earlyprintk supportIt's incredibly difficult to diagnose early EFI boot issues withoutspecial hardware because earlyprintk=vga doesn't work on EFI systems.Add support for writing to the EFI framebuffer, via earlyprintk=efi,which will actually give users a chance of providing debug output.Cc: H. Peter Anvin Acked-by: Ingo Molnar Cc: Thomas Gleixner Cc: Peter Jones Signed-off-by: Matt Fleming List of files: /linux-6.15/arch/x86/platform/efi/Makefile

2223af38 - efi: Fix the ACPI BGRT driver for images located in EFI boot services memory

Sat, 29 Sep 2012 00:57:05 +0000

efi: Fix the ACPI BGRT driver for images located in EFI boot services memoryThe ACPI BGRT driver accesses the BIOS logo image when it initializes.However, ACPI 5.0 (which introduces the BGRT) recommends putting thelogo image in EFI boot services memory, so that the OS can reclaim thatmemory. Production systems follow this recommendation, breaking theACPI BGRT driver.Move the bulk of the BGRT code to run during a new EFI lateinitialization phase, which occurs after switching EFI to virtual mode,and after initializing ACPI, but before freeing boot services memory.Copy the BIOS logo image to kernel memory at that point, and make itaccessible to the BGRT driver. Rework the existing ACPI BGRT driver toact as a simple wrapper exposing that image (and the properties from theBGRT) via sysfs.Signed-off-by: Josh Triplett Link: http://lkml.kernel.org/r/93ce9f823f1c1f3bb88bdd662cce08eee7a17f5d.1348876882.git.josh@joshtriplett.orgSigned-off-by: H. Peter Anvin List of files: /linux-6.15/arch/x86/platform/efi/Makefile

b17ed480 - x86: Move efi to platform

Sat, 16 Oct 2010 08:19:54 +0000

x86: Move efi to platformSigned-off-by: Thomas Gleixner Cc: Huang Ying List of files: /linux-6.15/arch/x86/platform/efi/Makefile