在 2024/3/30 9:52, Dan Williams 写道:
Shiyang Ruan wrote:
Poison injection from debugfs is silent too. Add calling
cxl_mem_report_poison() to make it able to do memory_failure().
Why does this needs to be signalled? It is a debug interface, the
debugger can also trigger a read after the injec
Shiyang Ruan wrote:
> Poison injection from debugfs is silent too. Add calling
> cxl_mem_report_poison() to make it able to do memory_failure().
Why does this needs to be signalled? It is a debug interface, the
debugger can also trigger a read after the injection, or trigger page
soft-offline.
On Fri, Mar 29, 2024 at 02:36:12PM +0800, Shiyang Ruan wrote:
> Poison injection from debugfs is silent too. Add calling
> cxl_mem_report_poison() to make it able to do memory_failure().
Curious as to why it is silent? Will a GMER poison event occur
and trigger the path to report it via memory_fa
Poison injection from debugfs is silent too. Add calling
cxl_mem_report_poison() to make it able to do memory_failure().
Signed-off-by: Shiyang Ruan
---
drivers/cxl/core/memdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c
index e976
