From: Ben Widawsky <ben.widawsky@intel.com>
To: linux-cxl@vger.kernel.org
Cc: patches@lists.linux.dev, Ben Widawsky <ben.widawsky@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: [RFC PATCH 0/2] Region creation/configuration ABI
Date: Thu, 24 Feb 2022 22:00:36 -0800 [thread overview]
Message-ID: <20220225060038.1511562-1-ben.widawsky@intel.com> (raw)
I'm looking for feedback on the next generation of the region configuration and
creation ABI. The primary changes from the v3 posting of the region driver [1]
are:
- Decoders instead of memdevs for targets
- Substantial rework around creation
- configuration sanitization at ABI boundary
- teardown region on memdev/decoder removal
With the new changes, it makes the most sense to rework the series so that
existing region enumeration (setup by boot firmware) be done prior to allowing
region creation. This is because the changes requested will require claiming
resources at configuration time rather than region->probe() time.
That said, these patches do reflect the proposed ABI and they can be reviewed in
parallel with that work. I'd appreciate feedback around whether the proposed ABI
is missing anything, and, whether there are inherent flaws in the
implementation.
[1]: https://lore.kernel.org/linux-cxl/20220128002707.391076-1-ben.widawsky@intel.com/
Ben Widawsky (2):
cxl/region: Add region creation ABI
cxl/region: Introduce concept of region configuration
Documentation/ABI/testing/sysfs-bus-cxl | 82 +++
.../driver-api/cxl/memory-devices.rst | 11 +
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 3 +
drivers/cxl/core/port.c | 26 +
drivers/cxl/core/region.c | 568 ++++++++++++++++++
drivers/cxl/cxl.h | 21 +-
drivers/cxl/region.h | 93 +++
tools/testing/cxl/Kbuild | 1 +
9 files changed, 805 insertions(+), 1 deletion(-)
create mode 100644 drivers/cxl/core/region.c
create mode 100644 drivers/cxl/region.h
base-commit: 3bdf187d313e067de2a81109f9a1dd3da7f3dc2c
--
2.35.1
next reply other threads:[~2022-02-25 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 6:00 Ben Widawsky [this message]
2022-02-25 6:00 ` [RFC PATCH 1/2] cxl/region: Add region creation ABI Ben Widawsky
2022-02-28 23:48 ` Dan Williams
2022-03-01 21:22 ` Ben Widawsky
2022-03-01 21:36 ` Ben Widawsky
2022-03-01 21:49 ` Dan Williams
2022-02-25 6:00 ` [RFC PATCH 2/2] cxl/region: Introduce concept of region configuration Ben Widawsky
2022-03-01 1:16 ` Dan Williams
2022-03-01 17:43 ` Ben Widawsky
2022-03-01 18:34 ` Dan Williams
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=20220225060038.1511562-1-ben.widawsky@intel.com \
--to=ben.widawsky@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.