linux-kernel - Re: [PATCH v2 1/3] drivers/cxl: introduce cxl_region_driver field for cxl

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: <aXvGYJjULVhNiEMV@gourry-fedora-PF4VCD3F>
Date: Thu, 29 Jan 2026 15:43:12 -0500
From: Gregory Price <gourry@...rry.net>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: linux-cxl@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel-team@...a.com, jonathan.cameron@...wei.com,
	dave.jiang@...el.com, alison.schofield@...el.com,
	vishal.l.verma@...el.com, ira.weiny@...el.com,
	dan.j.williams@...el.com, anisa.su@...sung.com,
	dongjoo.seo1@...sung.com, s.neeraj@...sung.com
Subject: Re: [PATCH v2 1/3] drivers/cxl: introduce cxl_region_driver field
 for cxl_region

On Thu, Jan 29, 2026 at 11:10:39AM -0800, Davidlohr Bueso wrote:
> On Tue, 13 Jan 2026, Gregory Price wrote:
> 
> > The CXL driver presently has 3 modes of managing a cxl_region:
> >  - no specific driver (bios-onlined SystemRAM)
> >  - dax_region (all other RAM regions, for now)
> >  - pmem_region (all PMEM regions)
> > 
> > Formalize these into specific "region drivers".
> 
> I think your overall idea of these region driver backends to isolate use
> cases makes a lot of sense and helps untangle things. This series is a good
> step and nicely moves ad-hoc complexity out of region.c.
> 

fyi this is being respun entirely to include the end-to-end solution
described here:

https://lore.kernel.org/linux-cxl/aXErSP1zKnv4koKG@gourry-fedora-PF4VCD3F/

Posting shortly

~Gregory