linux-kernel - Re: [PATCH v9 7/7] ACPI: APEI: EINJ: Update the documentation for EINJv2 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <684c628eb0605_224f6a29415@iweiny-mobl.notmuch>
Date: Fri, 13 Jun 2025 12:40:30 -0500
From: Ira Weiny <ira.weiny@...el.com>
To: Zaid Alali <zaidal@...amperecomputing.com>, <rafael@...nel.org>,
	<lenb@...nel.org>, <james.morse@....com>, <tony.luck@...el.com>,
	<bp@...en8.de>, <kees@...nel.org>, <gustavoars@...nel.org>,
	<Jonathan.Cameron@...wei.com>, <sudeep.holla@....com>,
	<jonathanh@...dia.com>, <u.kleine-koenig@...libre.com>,
	<dan.carpenter@...aro.org>, <viro@...iv.linux.org.uk>, <ira.weiny@...el.com>,
	<alison.schofield@...el.com>, <dan.j.williams@...el.com>,
	<gregkh@...uxfoundation.org>, <peterz@...radead.org>, <dave.jiang@...el.com>,
	<Benjamin.Cheatham@....com>, <linux-acpi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <linux-hardening@...r.kernel.org>
Subject: Re: [PATCH v9 7/7] ACPI: APEI: EINJ: Update the documentation for
 EINJv2 support

Zaid Alali wrote:
> Add documentation based on implemenation of EINJv2 as described in ACPI
			     implementation

> 6.5.A specification.
> 
> Link: https://uefi.org/specs/ACPI/6.5_A/18_Platform_Error_Interfaces.html#error-injection
> 
> [Tony: New user interface for device id and syndrome]
> 
> Co-developed-by: Tony Luck <tony.luck@...el.com>
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> Signed-off-by: Zaid Alali <zaidal@...amperecomputing.com>
> ---
>  .../firmware-guide/acpi/apei/einj.rst         | 33 +++++++++++++++++++
>  1 file changed, 33 insertions(+)
> 
> diff --git a/Documentation/firmware-guide/acpi/apei/einj.rst b/Documentation/firmware-guide/acpi/apei/einj.rst
> index c52b9da08fa9..7d8435d35a18 100644
> --- a/Documentation/firmware-guide/acpi/apei/einj.rst
> +++ b/Documentation/firmware-guide/acpi/apei/einj.rst
> @@ -59,6 +59,9 @@ The following files belong to it:
>    0x00000200        Platform Correctable
>    0x00000400        Platform Uncorrectable non-fatal
>    0x00000800        Platform Uncorrectable fatal
> +  V2_0x00000001     EINJV2 Processor Error
> +  V2_0x00000002     EINJV2 Memory Error
> +  V2_0x00000004     EINJV2 PCI Express Error
>    ================  ===================================
>  
>    The format of the file contents are as above, except present are only
> @@ -88,6 +91,8 @@ The following files belong to it:
>        Memory address and mask valid (param1 and param2).
>      Bit 2
>        PCIe (seg,bus,dev,fn) valid (see param4 below).
> +    Bit 3
> +      EINJv2 extension structure is valid
>  
>    If set to zero, legacy behavior is mimicked where the type of
>    injection specifies just one bit set, and param1 is multiplexed.
> @@ -122,6 +127,13 @@ The following files belong to it:
>    this actually works depends on what operations the BIOS actually
>    includes in the trigger phase.
>  
> +- component_id0 .. component_idN, component_syndrome0 .. component_syndromeN
> +
> +  These files are used to set the "Component Array" field
> +  of the EINJv2 Extension Structure. Each holds a 128-bit
> +  hex value. Writing just a newline to any of these files
> +  sets an invalid (all-ones) value.

I guess I missed the all-ones value being set.  :-/

Ira

> +
>  CXL error types are supported from ACPI 6.5 onwards (given a CXL port
>  is present). The EINJ user interface for CXL error types is at
>  <debugfs mount point>/cxl. The following files belong to it:
> @@ -194,6 +206,27 @@ An error injection example::
>    # echo 0x8 > error_type			# Choose correctable memory error
>    # echo 1 > error_inject			# Inject now
>  
> +An EINJv2 error injection example::
> +
> +  # cd /sys/kernel/debug/apei/einj
> +  # cat available_error_type			# See which errors can be injected
> +  0x00000002	Processor Uncorrectable non-fatal
> +  0x00000008	Memory Correctable
> +  0x00000010	Memory Uncorrectable non-fatal
> +  V2_0x00000001	EINJV2 Processor Error
> +  V2_0x00000002	EINJV2 Memory Error
> +
> +  # echo 0x12345000 > param1			# Set memory address for injection
> +  # echo 0xfffffffffffff000 > param2		# Range - anywhere in this page
> +  # echo 0x1 > component_id0			# First device ID
> +  # echo 0x4 > component_syndrome0		# First error syndrome
> +  # echo 0x2 > component_id1			# Second device ID
> +  # echo 0x4 > component_syndrome1		# Second error syndrome
> +  # echo '' > component_id2			# Mark id2 invalid to terminate list
> +  # echo V2_0x2 > error_type			# Choose EINJv2 memory error
> +  # echo 0xa > flags				# set flags to indicate EINJv2
> +  # echo 1 > error_inject			# Inject now
> +
>  You should see something like this in dmesg::
>  
>    [22715.830801] EDAC sbridge MC3: HANDLING MCE MEMORY ERROR
> -- 
> 2.43.0
>