From: Ben Widawsky <ben.widawsky@intel.com>
To: linux-cxl@vger.kernel.org
Cc: 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: [PATCH 0/6] CXL core reorganization
Date: Thu, 15 Jul 2021 12:41:19 -0700 [thread overview]
Message-ID: <20210715194125.898305-1-ben.widawsky@intel.com> (raw)
The main motivation of the patch series is to establish the cxl_core driver in
its own directory and modularize it. Specifically, the patch series aims to
achieve three things:
1. Move existing core functionality to a new directory.
2. Split existing core functionality into multiple files.
3. Migrate memdev functionality into core.
#1 is trivially accomplished with git mv. The file itself is renamed back to
bus.c since the goal is to break up core functionality into multiple files, and
so the name core.c doesn't make sense in that context.
#2 is also trivially accomplished via cut/paste.
#3 is slightly invasive in that it has certain functional changes to improve the
existing interfaces and make them more generic. The rest of the change is
cut/paste. This is also the only part of the series which has runtime functional
change in that some interfaces are removed from cxl_pci, moved into cxl_core,
and exported for other drivers to use.
Ben Widawsky (6):
cxl: Move cxl_core to new directory
cxl/core: Improve CXL core kernel docs
cxl/core: Extract register and pmem functionality
cxl/mem: Move character device region creation
cxl: Pass fops and shutdown to memdev creation
cxl/core: Move memdev management to core
.../driver-api/cxl/memory-devices.rst | 8 +-
drivers/cxl/Makefile | 2 +-
drivers/cxl/{core.c => core/bus.c} | 458 +-----------------
drivers/cxl/core/core.h | 20 +
drivers/cxl/core/memdev.c | 224 +++++++++
drivers/cxl/core/pmem.c | 201 ++++++++
drivers/cxl/core/regs.c | 235 +++++++++
drivers/cxl/mem.h | 9 +
drivers/cxl/pci.c | 239 +--------
9 files changed, 731 insertions(+), 665 deletions(-)
rename drivers/cxl/{core.c => core/bus.c} (58%)
create mode 100644 drivers/cxl/core/core.h
create mode 100644 drivers/cxl/core/memdev.c
create mode 100644 drivers/cxl/core/pmem.c
create mode 100644 drivers/cxl/core/regs.c
--
2.32.0
next reply other threads:[~2021-07-15 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 19:41 Ben Widawsky [this message]
2021-07-15 19:41 ` [PATCH 1/6] cxl: Move cxl_core to new directory Ben Widawsky
2021-07-15 22:44 ` Dan Williams
2021-07-20 18:07 ` [PATCH v2 " Ben Widawsky
2021-07-20 18:14 ` Ben Widawsky
2021-07-15 19:41 ` [PATCH 2/6] cxl/core: Improve CXL core kernel docs Ben Widawsky
2021-07-15 23:46 ` Dan Williams
2021-07-15 19:41 ` [PATCH 3/6] cxl/core: Extract register and pmem functionality Ben Widawsky
2021-07-28 22:14 ` Dan Williams
2021-07-15 19:41 ` [PATCH 4/6] cxl/mem: Move character device region creation Ben Widawsky
2021-07-28 22:34 ` Dan Williams
2021-07-15 19:41 ` [PATCH 5/6] cxl: Pass fops and shutdown to memdev creation Ben Widawsky
2021-07-28 23:21 ` Dan Williams
2021-07-15 19:41 ` [PATCH 6/6] cxl/core: Move memdev management to core Ben Widawsky
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=20210715194125.898305-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=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;
as well as URLs for NNTP newsgroup(s).