From: Huang Ying <ying.huang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Huang Ying <ying.huang@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Alejandro Lucero <alucerop@amd.com>
Subject: [RFC 0/5] cxl: Preparation of type2 accelerators support
Date: Wed, 25 Sep 2024 10:46:42 +0800 [thread overview]
Message-ID: <20240925024647.46735-1-ying.huang@intel.com> (raw)
There have been 2 series to add type 2 accelerators support in [1] and [2].
[1] https://lore.kernel.org/linux-cxl/168592149709.1948938.8663425987110396027.stgit@dwillia2-xfh.jf.intel.com/
[2] https://lore.kernel.org/linux-cxl/20240516081202.27023-1-alucerop@amd.com/
Both provide relative complete support, but both are long too. To
make it easier to review, some preparation of type2 accelerators
support is implemented in this series. More complete support can be
implemented based on it.
This series has been tested with cxl_test via mocking a type2
accelerator as in [1] above. Because more type2 accelerators support
than that provided by this series is needed to simulate the device,
the cxl_test patch isn't included in the series.
Huang Ying (5):
cxl: Rename ACPI_CEDT_CFMWS_RESTRICT_TYPE2/TYPE3
cxl: Rename CXL_DECODER_HOSTONLYMEM/DEVMEM
cxl: Separate coherence from target type
cxl: Set type of region to that of the first endpoint
cxl: Avoid to create dax regions for type2 accelerators
drivers/cxl/acpi.c | 9 +++---
drivers/cxl/core/hdm.c | 38 +++++++++++++----------
drivers/cxl/core/mbox.c | 1 +
drivers/cxl/core/port.c | 17 ++++++-----
drivers/cxl/core/region.c | 58 ++++++++++++++++++++++++++++++------
drivers/cxl/cxl.h | 28 +++++++++++------
drivers/cxl/cxlmem.h | 11 +++++++
include/acpi/actbl1.h | 10 +++----
tools/testing/cxl/test/cxl.c | 24 +++++++--------
9 files changed, 133 insertions(+), 63 deletions(-)
Best Regards,
Huang, Ying
next reply other threads:[~2024-09-25 2:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 2:46 Huang Ying [this message]
2024-09-25 2:46 ` [RFC 1/5] cxl: Rename ACPI_CEDT_CFMWS_RESTRICT_TYPE2/TYPE3 Huang Ying
2024-10-01 2:48 ` Davidlohr Bueso
2024-10-01 13:43 ` Gregory Price
2024-09-25 2:46 ` [RFC 2/5] cxl: Rename CXL_DECODER_HOSTONLYMEM/DEVMEM Huang Ying
2024-10-01 3:01 ` Davidlohr Bueso
2024-10-01 13:45 ` Gregory Price
2024-09-25 2:46 ` [RFC 3/5] cxl: Separate coherence from target type Huang Ying
2024-10-01 13:53 ` Gregory Price
2024-10-02 0:41 ` Huang, Ying
2024-10-11 2:40 ` Huang, Ying
2024-10-02 21:15 ` Ben Cheatham
2024-10-03 1:13 ` Huang, Ying
2024-09-25 2:46 ` [RFC 4/5] cxl: Set type of region to that of the first endpoint Huang Ying
2024-10-01 13:56 ` Gregory Price
2024-10-02 0:40 ` Huang, Ying
2024-10-02 21:15 ` Ben Cheatham
2024-10-03 1:12 ` Huang, Ying
2024-10-03 14:28 ` Ben Cheatham
2024-09-25 2:46 ` [RFC 5/5] cxl: Avoid to create dax regions for type2 accelerators Huang Ying
2024-10-01 13:57 ` Gregory Price
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=20240925024647.46735-1-ying.huang@intel.com \
--to=ying.huang@intel.com \
--cc=alison.schofield@intel.com \
--cc=alucerop@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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