linux-kernel - Re: CXL Boot to Bash - Section 2a (Drivers): CXL Decoder Programming

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2cec2f4b-d68b-40e8-8cd9-283eaaec8164@fujitsu.com>
Date: Tue, 11 Mar 2025 02:48:39 +0000
From: "Zhijian Li (Fujitsu)" <lizhijian@...itsu.com>
To: Gregory Price <gourry@...rry.net>
CC: "lsf-pc@...ts.linux-foundation.org" <lsf-pc@...ts.linux-foundation.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>, "linux-cxl@...r.kernel.org"
	<linux-cxl@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: Re: CXL Boot to Bash - Section 2a (Drivers): CXL Decoder Programming



On 07/03/2025 23:07, Gregory Price wrote:
> So this is just some semantic confusion - and the reality is the driver
> simply refers to the first device in the fabric as "The Root", and every
> device has "A Port", and so the "Root Port" just means it's the Root's
> "Port" not a "CXL Specification Root Port".
> 
> Whatever the case, from the snippets above, you can see the CFMWS adds 1
> "root decoder" per CFMWS - which makes sense, as a CFMWS can describe
> multi-host-bridge interleave - i.e. whatever the actual root device is
> must be upstream of the host bridges themselves.

Gregory,

Many thanks for your detailed explanation. This aligns with what I understood before.

Thanks
Zhijian