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: <aSYZ7t9QrxiAsyL4@gourry-fedora-PF4VCD3F>
Date: Tue, 25 Nov 2025 16:04:46 -0500
From: Gregory Price <gourry@...rry.net>
To: Alison Schofield <alison.schofield@...el.com>
Cc: Robert Richter <rrichter@....com>,
	Vishal Verma <vishal.l.verma@...el.com>,
	Ira Weiny <ira.weiny@...el.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Jonathan Cameron <jonathan.cameron@...wei.com>,
	Dave Jiang <dave.jiang@...el.com>,
	Davidlohr Bueso <dave@...olabs.net>, linux-cxl@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>,
	Terry Bowman <terry.bowman@....com>,
	Joshua Hahn <joshua.hahnjy@...il.com>
Subject: Re: [PATCH v6 00/11] cxl: ACPI PRM Address Translation Support and
 AMD Zen5 enablement

On Tue, Nov 25, 2025 at 08:37:33AM -0800, Alison Schofield wrote:
> On Tue, Nov 25, 2025 at 08:54:58AM -0500, Gregory Price wrote:
> 
> Could be your devices don't support inject or clear. At init time we set
> the bits inidicating what poison opcodes the device supports, see
> cxl_set_poison_cmd_enabled().
> 50d527f52cbf ("cxl/mem: Add debugfs attributes for poison inject and clear")
> 
> Devices may support list but not inject and clear. Look for this attribute:
> /sys/bus/cxl/devices/memX/trigger_poison_list. If that is present, then a
> quicker, maybe fruitful check, may be 'cxl list -M --media-errors'. If you're
> lucky ;) your devices come pre-loaded with poison. That cmd will emit the
> poisoned DPAs and if part of a region, the SPAs too. cxl-list is getting that
> all from the kernel trace log, so if you don't have 'cxl list', just trigger
> directly and examine the trace log.
> 

Unfortunately it appears my devices do not support any of this :[

[ /sys/kernel/debug/cxl]$ ls mem0/
dpamem

Is all I have

~Gregory

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ