linux-kernel - Re: [LSF/MM] CXL Boot to Bash - Section 0: ACPI and Linux Resources

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z-VGN79KVjuRg41K@gourry-fedora-PF4VCD3F>
Date: Thu, 27 Mar 2025 08:36:07 -0400
From: Gregory Price <gourry@...rry.net>
To: Yuquan Wang <wangyuquan1236@...tium.com.cn>
Cc: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	lsf-pc@...ts.linux-foundation.org, linux-mm@...ck.org,
	linux-cxl@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [LSF/MM] CXL Boot to Bash - Section 0: ACPI and Linux Resources

On Thu, Mar 27, 2025 at 05:34:54PM +0800, Yuquan Wang wrote:
> 
> In the future, srat.c would add one seperate NUMA node for each
> Generic Port in SRAT.
> 
> System firmware should know the performance characteristics between
> CPU/GI to the GP, and the static HMAT should include this coordinate.
> 
> Is my understanding right?
> 
> 

HMAT is static configuration data.  A GI/GP might not have its
performance data known until the device is added.  In this case, the
HMAT may only contain generic (inaccurate) information - or more likely
just nothing.  It's up to the platform vendor.

~Gregory