Changes in Makefile

12fb28ea - EINJ: Add CXL error type support

Mon, 11 Mar 2024 14:25:06 +0000

EINJ: Add CXL error type supportMove CXL protocol error types from einj.c (now einj-core.c) to einj-cxl.c.einj-cxl.c implements the necessary handling for CXL protocol errorinjection and exposes an API for the CXL core to use said functionality,while also allowing the EINJ module to be built without CXL support.Because CXL error types targeting CXL 1.0/1.1 ports require specialhandling, only allow them to be injected through the new cxl debugfsinterface (next commit) and return an error when attempting to injectthrough the legacy interface.Reviewed-by: Jonathan Cameron Signed-off-by: Ben Cheatham Link: https://lore.kernel.org/r/20240311142508.31717-3-Benjamin.Cheatham@amd.comSigned-off-by: Dan Williams List of files: /linux-6.15/drivers/acpi/apei/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/drivers/acpi/apei/Makefile

a3e2acc5 - ACPI / APEI: Add Boot Error Record Table (BERT) support

Wed, 29 Jun 2016 20:04:29 +0000

ACPI / APEI: Add Boot Error Record Table (BERT) supportACPI/APEI is designed to verifiy/report H/W errors, like CorrectedError(CE) and Uncorrected Error(UC). It contains four tables: HEST,ERST, EINJ and BERT. The first three tables have been merged fora long time, but because of lacking BIOS support for BERT, thesupport for BERT is pending until now. Recently on ARM 64 platformit is has been supported. So here we come.Under normal circumstances, when a hardware error occurs, kernel willbe notified via NMI, MCE or some other method, then kernel willprocess the error condition, report it, and recover it if possible.But sometime, the situation is so bad, so that firmware may choose toreset directly without notifying Linux kernel.Linux kernel can use the Boot Error Record Table (BERT) to get theun-notified hardware errors that occurred in a previous boot. In thispatch, the error information is reported via printk.For more information about BERT, please refer to ACPI Specificationversion 6.0, section 18.3.1: http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdfThe following log is a BERT record after system reboot because of hittinga fatal memory error:BERT: Error records from previous boot:[Hardware Error]: It has been corrected by h/w and requires no further action[Hardware Error]: event severity: corrected[Hardware Error]: Error 0, type: recoverable[Hardware Error]: section_type: memory error[Hardware Error]: error_status: 0x0000000000000400[Hardware Error]: physical_address: 0xffffffffffffffff[Hardware Error]: card: 1 module: 2 bank: 3 row: 1 column: 2 bit_position: 5[Hardware Error]: error_type: 2, single-bit ECC[Tomasz Nowicki: Clear error status at the end of error handling][Tony: Applied some cleanups suggested by Fu Wei][Fu Wei: delete EXPORT_SYMBOL_GPL(bert_disable), improve the code]Signed-off-by: Huang Ying Signed-off-by: Tomasz Nowicki Signed-off-by: Chen, Gong Tested-by: Jonathan (Zhixiong) Zhang Signed-off-by: Fu Wei Tested-by: Tyler Baicar Reviewed-by: Borislav Petkov Signed-off-by: Tony Luck Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/acpi/apei/Makefile

7ea6c6c1 - Move cper.c from drivers/acpi/apei to drivers/firmware/efi

Mon, 28 Oct 2013 21:06:55 +0000

Move cper.c from drivers/acpi/apei to drivers/firmware/eficper.c contains code to decode and print "Common Platform Error Records".Originally added under drivers/acpi/apei because the only user was in thatsame directory - but now we have another consumer, and we shouldn't haveto force CONFIG_ACPI_APEI get access to this code.Since CPER is defined in the UEFI specification - the logical home forthis code is under drivers/firmware/efi/Acked-by: Matt Fleming Acked-by: Ingo Molnar Signed-off-by: Tony Luck List of files: /linux-6.15/drivers/acpi/apei/Makefile

2ff729d5 - ACPI, APEI, ERST debug support

Thu, 12 Aug 2010 03:55:17 +0000

ACPI, APEI, ERST debug supportThis patch adds debugging/testing support to ERST. A misc device isimplemented to export raw ERST read/write/clear etc operations to userspace. With this patch, we can add ERST testing support tolinuxfirmwarekit ISO (linuxfirmwarekit.org) to verify the kernelsupport and the firmware implementation.Signed-off-by: Huang Ying Acked-by: Randy Dunlap Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

a08f82d0 - ACPI, APEI, Error Record Serialization Table (ERST) support

Tue, 18 May 2010 06:35:21 +0000

ACPI, APEI, Error Record Serialization Table (ERST) supportERST is a way provided by APEI to save and retrieve hardware errorrecord to and from some simple persistent storage (such as flash).The Linux kernel support implementation is quite simple and workablein NMI context. So it can be used to save hardware error record intoflash in hardware error exception or NMI handler, where other morecomplex persistent storage such as disk is not usable. After savinghardware error records via ERST in hardware error exception or NMIhandler, the error records can be retrieved and logged into disk ornetwork after a clean reboot.For more information about ERST, please refer to ACPI Specificationversion 4.0, section 17.4.This patch incorporate fixes from Jin Dongming.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen CC: Jin Dongming Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

d334a491 - ACPI, APEI, Generic Hardware Error Source memory error support

Tue, 18 May 2010 06:35:20 +0000

ACPI, APEI, Generic Hardware Error Source memory error supportGeneric Hardware Error Source provides a way to report platformhardware errors (such as that from chipset). It works in so called"Firmware First" mode, that is, hardware errors are reported tofirmware firstly, then reported to Linux by firmware. This way, somenon-standard hardware error registers or non-standard hardware linkcan be checked by firmware to produce more valuable hardware errorinformation for Linux.Now, only SCI notification type and memory errors are supported. Morenotification type and hardware error type will be added later. Thesememory errors are reported to user space through /dev/mcelog viafaking a corrected Machine Check, so that the error memory page can beofflined by /sbin/mcelog if the error count for one page is beyond thethreshold.On some machines, Machine Check can not report physical address forsome corrected memory errors, but GHES can do that. So this simplifiedGHES is implemented firstly.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

06d65dea - ACPI, APEI, UEFI Common Platform Error Record (CPER) header

Tue, 18 May 2010 06:35:19 +0000

ACPI, APEI, UEFI Common Platform Error Record (CPER) headerCPER stands for Common Platform Error Record, it is the hardware errorrecord format used to describe platform hardware error by various APEItables, such as ERST, BERT and HEST etc.For more information about CPER, please refer to Appendix N of UEFISpecification version 2.3.This patch mainly includes the data structure difinition header fileused by other files.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

e4021345 - ACPI, APEI, EINJ support

Tue, 18 May 2010 06:35:14 +0000

ACPI, APEI, EINJ supportEINJ provides a hardware error injection mechanism, this is useful fordebugging and testing of other APEI and RAS features.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

9dc96664 - ACPI, APEI, HEST table parsing

Tue, 18 May 2010 06:35:13 +0000

ACPI, APEI, HEST table parsingHEST describes error sources in detail; communicating operationalparameters (i.e. severity levels, masking bits, and threshold values)to OS as necessary. It also allows the platform to report errorsources for which OS would typically not implement support (forexample, chipset-specific error registers).HEST information may be needed by other subsystems. For example, HESTPCIE AER error source information describes whether a PCIE root portworks in "firmware first" mode, this is needed by general PCIE AERerror subsystem. So a public HEST tabling parsing interface isprovided.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile

a643ce20 - ACPI, APEI, APEI supporting infrastructure

Tue, 18 May 2010 06:35:12 +0000

ACPI, APEI, APEI supporting infrastructureAPEI stands for ACPI Platform Error Interface, which allows to reporterrors (for example from the chipset) to the operating system. Thisimproves NMI handling especially. In addition it supports errorserialization and error injection.For more information about APEI, please refer to ACPI Specificationversion 4.0, chapter 17.This patch provides some common functions used by more than one APEItables, mainly framework of interpreter for EINJ and ERST.A machine readable language is defined for EINJ and ERST for OS toexecute, and so to drive the firmware to fulfill the correspondingfunctions. The machine language for EINJ and ERST is compatible, so acommon framework is defined for them.Signed-off-by: Huang Ying Signed-off-by: Andi Kleen Signed-off-by: Len Brown List of files: /linux-6.15/drivers/acpi/apei/Makefile