<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/edac/skx_common.c, branch linux-5.18.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.18.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.18.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2021-08-23T17:35:36Z</updated>
<entry>
<title>EDAC/i10nm: Retrieve and print retry_rd_err_log registers</title>
<updated>2021-08-23T17:35:36Z</updated>
<author>
<name>Youquan Song</name>
</author>
<published>2021-08-18T17:57:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cf4e6d52f58399c777276172ec250502e19d5e63'/>
<id>urn:sha1:cf4e6d52f58399c777276172ec250502e19d5e63</id>
<content type='text'>
Retrieve and print retry_rd_err_log registers like the earlier change:
commit e80634a75aba ("EDAC, skx: Retrieve and print retry_rd_err_log registers")

This is a little trickier than on Skylake because of potential
interference with BIOS use of the same registers. The default
behavior is to ignore these registers.

A module parameter retry_rd_err_log(default=0) controls the mode of operation:
- 0=off  : Default.
- 1=bios : Linux doesn't reset any control bits, but just reports values.
           This is "no harm" mode, but it may miss reporting some data.
- 2=linux: Linux tries to take control and resets mode bits,
           clears valid/UC bits after reading. This should be
           more reliable (especially if BIOS interference is reduced
           by disabling eMCA reporting mode in BIOS setup).

Co-developed-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Youquan Song &lt;youquan.song@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Link: https://lore.kernel.org/r/20210818175701.1611513-3-tony.luck@intel.com
</content>
</entry>
<entry>
<title>EDAC/skx_common: Set the memory type correctly for HBM memory</title>
<updated>2021-08-23T17:32:32Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2021-07-20T16:30:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fd07a4a0d30b5468a1f4a0739e34f5f014df7d44'/>
<id>urn:sha1:fd07a4a0d30b5468a1f4a0739e34f5f014df7d44</id>
<content type='text'>
Set the memory type to MEM_HBM2 if it's managed by the HBM2
memory controller.

Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Link: https://lore.kernel.org/r/20210720163009.GA1417532@agluck-desk2.amr.corp.intel.com
</content>
</entry>
<entry>
<title>EDAC/i10nm: Add support for high bandwidth memory</title>
<updated>2021-06-18T01:19:39Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2021-06-11T17:01:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c945088384d00e6eb61535cc4ba25bc062090909'/>
<id>urn:sha1:c945088384d00e6eb61535cc4ba25bc062090909</id>
<content type='text'>
A future Xeon processor will include in-package HBM (high bandwidth
memory). The in-package HBM memory controller shares the same
architecture with the regular DDR memory controller.

Add the HBM memory controller devices for EDAC support.

Tested-by: Hongyu Ning &lt;hongyu.ning@linux.intel.com&gt;
Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Link: https://lore.kernel.org/r/20210611170123.1057025-4-tony.luck@intel.com
</content>
</entry>
<entry>
<title>EDAC/skx_common: Add new ADXL components for 2-level memory</title>
<updated>2021-06-18T01:19:22Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2021-06-11T17:01:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2f4348e5a86198704368a699a7c4cdeb21d569f5'/>
<id>urn:sha1:2f4348e5a86198704368a699a7c4cdeb21d569f5</id>
<content type='text'>
Some Intel servers may configure memory in 2 levels, using
fast "near" memory (e.g. DDR) as a cache for larger, slower,
"far" memory (e.g. 3D X-point).

In these configurations the BIOS ADXL address translation for
an address in a 2-level memory range will provide details of
both the "near" and far components.

Current exported ADXL components are only for 1-level memory
system or for 2nd level memory of 2-level memory system. So
add new ADXL components for 1st level memory of 2-level memory
system to fully support 2-level memory system and the detection
of memory error source(1st level memory or 2nd level memory).

Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Link: https://lore.kernel.org/r/20210611170123.1057025-2-tony.luck@intel.com
</content>
</entry>
<entry>
<title>EDAC/i10nm: Add Intel Sapphire Rapids server support</title>
<updated>2020-11-19T20:57:26Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2020-11-17T12:49:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=479f58dda25bb46daeb937f124718e8b4aea6781'/>
<id>urn:sha1:479f58dda25bb46daeb937f124718e8b4aea6781</id>
<content type='text'>
The Sapphire Rapids CPU model shares the same memory controller
architecture with Ice Lake server. There are some configurations
different from Ice Lake server as below:
- The device ID for configuration agent.
- The size for per channel memory-mapped I/O.
- The DDR5 memory support.
So add the above configurations and the Sapphire Rapids CPU model
ID for EDAC support.

Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
</content>
</entry>
<entry>
<title>EDAC/{i7core,sb,pnd2,skx}: Fix error event severity</title>
<updated>2020-08-18T13:40:30Z</updated>
<author>
<name>Tony Luck</name>
</author>
<published>2020-07-07T19:43:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=45bc6098a3e279d8e391d22428396687562797e2'/>
<id>urn:sha1:45bc6098a3e279d8e391d22428396687562797e2</id>
<content type='text'>
IA32_MCG_STATUS.RIPV indicates whether the return RIP value pushed onto
the stack as part of machine check delivery is valid or not.

Various drivers copied a code fragment that uses the RIPV bit to
determine the severity of the error as either HW_EVENT_ERR_UNCORRECTED
or HW_EVENT_ERR_FATAL, but this check is reversed (marking errors where
RIPV is set as "FATAL").

Reverse the tests so that the error is marked fatal when RIPV is not set.

Reported-by: Gabriele Paoloni &lt;gabriele.paoloni@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;
Cc: &lt;stable@vger.kernel.org&gt;
Link: https://lkml.kernel.org/r/20200707194324.14884-1-tony.luck@intel.com
</content>
</entry>
<entry>
<title>Merge branch 'x86/entry' into ras/core</title>
<updated>2020-06-11T13:17:57Z</updated>
<author>
<name>Thomas Gleixner</name>
</author>
<published>2020-06-11T13:17:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f77d26a9fc525286bcef3d4f98b52e17482cf49c'/>
<id>urn:sha1:f77d26a9fc525286bcef3d4f98b52e17482cf49c</id>
<content type='text'>
to fixup conflicts in arch/x86/kernel/cpu/mce/core.c so MCE specific follow
up patches can be applied without creating a horrible merge conflict
afterwards.
</content>
</entry>
<entry>
<title>Merge branches 'edac-i10nm' and 'edac-misc' into edac-updates-for-5.8</title>
<updated>2020-06-01T09:39:15Z</updated>
<author>
<name>Borislav Petkov</name>
</author>
<published>2020-06-01T09:39:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2a02ca0428cfe68cce600111acb4c6f7d85cf71f'/>
<id>urn:sha1:2a02ca0428cfe68cce600111acb4c6f7d85cf71f</id>
<content type='text'>
Signed-off-by: Borislav Petkov &lt;bp@suse.de&gt;
</content>
</entry>
<entry>
<title>EDAC/skx: Use the mcmtr register to retrieve close_pg/bank_xor_enable</title>
<updated>2020-05-19T22:11:29Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2020-05-15T12:34:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1032095053b34d474aa20f2625d97dd306e0991b'/>
<id>urn:sha1:1032095053b34d474aa20f2625d97dd306e0991b</id>
<content type='text'>
The skx_edac driver wrongly uses the mtr register to retrieve two fields
close_pg and bank_xor_enable. Fix it by using the correct mcmtr register
to get the two fields.

Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Reported-by: Matthew Riley &lt;mattdr@google.com&gt;
Acked-by: Aristeu Rozanski &lt;aris@redhat.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Link: https://lore.kernel.org/r/20200515210146.1337-1-tony.luck@intel.com
</content>
</entry>
<entry>
<title>EDAC, {skx,i10nm}: Make some configurations CPU model specific</title>
<updated>2020-04-27T16:29:41Z</updated>
<author>
<name>Qiuxu Zhuo</name>
</author>
<published>2020-04-24T12:18:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ee5340abab3babb91c1807cea47de4468b2dfc91'/>
<id>urn:sha1:ee5340abab3babb91c1807cea47de4468b2dfc91</id>
<content type='text'>
The device ID for configuration agent PCI device and the offset for
bus number configuration register can be CPU model specific. So add
a new structure res_config to make them configurable and pass res_config
to {skx,i10nm}_init() and skx_get_all_bus_mappings() for use.

Signed-off-by: Qiuxu Zhuo &lt;qiuxu.zhuo@intel.com&gt;
Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;
Reviewed-by: Borislav Petkov &lt;bp@suse.de&gt;
Link: https://lore.kernel.org/r/20200427083246.GB11036@zn.tnic
</content>
</entry>
</feed>
