Re: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device

2024-08-09 Thread kernel test robot
patch link: https://lore.kernel.org/r/20240808151328.707869-3-ruansy.fnst%40fujitsu.com patch subject: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device config: x86_64-randconfig-121-20240809 (https://download.01.org/0day-ci/archive/20240809/202408091914.tfbjpunq-...@intel.com/co

Re: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device

2024-08-09 Thread kernel test robot
patch link: https://lore.kernel.org/r/20240808151328.707869-3-ruansy.fnst%40fujitsu.com patch subject: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device config: um-allyesconfig (https://download.01.org/0day-ci/archive/20240809/202408091537.p9rkx1r2-...@intel.com/config) compiler: gcc-12

Re: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device

2024-08-09 Thread kernel test robot
patch link: https://lore.kernel.org/r/20240808151328.707869-3-ruansy.fnst%40fujitsu.com patch subject: [PATCH v4 2/2] cxl: avoid duplicated report from MCE & device config: um-allmodconfig (https://download.01.org/0day-ci/archive/20240809/202408091543.unfvpffl-...@intel.com/config) compiler:

[PATCH v4 2/2] cxl: avoid duplicated report from MCE & device

2024-08-08 Thread Shiyang Ruan via
Since CXL device is a memory device, while CPU is consuming a poison page of CXL device, it always triggers a MCE (via interrupt #18) and calls memory_failure() to handle POISON page, no matter which-First path is configured. CXL device could also find and report the POISON, kernel now not only tr