RE: [PATCH 1/2] EDAC/skx_common: Distinguish the memory error source

[Luck, Tony]

> The current skx_common determines whether the memory error source is the
> near memory of the 2LM system and then retrieves the decoded error results
> from the ADXL components (near-memory vs. non-near-memory) accordingly.
>
> However, some memory controllers may have limitations in correctly
> reporting the memory error source, leading to the retrieval of incorrect
> decoded parts from the ADXL.
>
> To address these limitations, instead of simply determining whether the
> memory error is from the near memory of the 2LM system, it is necessary to
> distinguish the memory error source details as follows:
>
>   Memory error from the near memory of the 2LM system.
>   Memory error from the far memory of the 2LM system.
>   Memory error from the 1LM system.
>   Not a memory error.
>
> This will enable the i10nm_edac driver to take appropriate actions for
> those memory controllers that have limitations in reporting the memory
> error source.
>
> Fixes: ba987eaaabf9 ("EDAC/i10nm: Add Intel Granite Rapids server support")
> Tested-by: Diego Garcia Rodriguez <diego.garcia.rodriguez@xxxxxxxxx>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@xxxxxxxxx>


Applied (this one and part 2) to edac-drivers branch of RAS tree.

Thanks

-Tony