From: Gregory Price <gourry@gourry.net>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, jonathan.cameron@huawei.com,
dave.jiang@intel.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
dan.j.williams@intel.com, anisa.su@samsung.com,
dongjoo.seo1@samsung.com, s.neeraj@samsung.com
Subject: Re: [PATCH v2 1/3] drivers/cxl: introduce cxl_region_driver field for cxl_region
Date: Thu, 29 Jan 2026 15:43:12 -0500 [thread overview]
Message-ID: <aXvGYJjULVhNiEMV@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260129191039.kodgkum445ws5rhs@offworld>
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
prev parent reply other threads:[~2026-01-29 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:21 [PATCH v2 1/3] drivers/cxl: introduce cxl_region_driver field for cxl_region Gregory Price
2026-01-13 20:21 ` [PATCH v2 2/3] cxl/core/region: move pmem region driver logic into pmem_region Gregory Price
2026-01-13 21:18 ` Dave Jiang
2026-01-20 17:20 ` Fabio M. De Francesco
2026-01-13 20:21 ` [PATCH v2 3/3] cxl/core/region: move dax region driver logic into dax_region Gregory Price
2026-01-13 21:18 ` Dave Jiang
2026-01-20 17:26 ` Fabio M. De Francesco
2026-01-29 19:16 ` Davidlohr Bueso
2026-01-13 21:16 ` [PATCH v2 1/3] drivers/cxl: introduce cxl_region_driver field for cxl_region Dave Jiang
2026-01-14 18:15 ` Alison Schofield
2026-01-14 18:22 ` Gregory Price
2026-01-20 18:39 ` Fabio M. De Francesco
2026-01-21 22:27 ` Ira Weiny
2026-01-21 23:44 ` Gregory Price
2026-01-22 2:12 ` Gregory Price
2026-01-29 19:10 ` Davidlohr Bueso
2026-01-29 20:43 ` Gregory Price [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aXvGYJjULVhNiEMV@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=anisa.su@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=dongjoo.seo1@samsung.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kernel-team@meta.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.neeraj@samsung.com \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox