From: alison.schofield@intel.com
To: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH v4 0/3] Add DPA->HPA translation to dram & general_media events
Date: Thu, 25 Apr 2024 20:46:22 -0700 [thread overview]
Message-ID: <cover.1714102202.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
Changes in v4:
- Pick up Dan's style suggestions I missed in v3 (Dan)
- Lookup hpa earlier (within trace_enabled()) and pass to the event handler (Dan)
- Add and use a new member in cxl_event union to access the common phys_addr field.
Link to v3: https://lore.kernel.org/cover.1714085857.git.alison.schofield@intel.com/
Changes in v3:
- Harvest the cxlr before calling trace handler (Dan)
- Replace macros w inline fast assigns (made easier w available cxlr)
- Drop prior review (Jonathan) on Patch 3 due to churn.
- Remove Patch 4 which was making cxl_poison use the (now gone) macros.
(A uuid_t change was tucked in Patch 4 and can be posted as a separate
tidy-up patch.)
Link to v2: https://lore.kernel.org/cover.1713842838.git.alison.schofield@intel.com/
An update to the cxl_events unit test is in review here:
https://lore.kernel.org/20240328043727.2186722-1-alison.schofield@intel.com/
Begin Cover Letter:
Add HPA translations to CXL events: cxl_dram and cxl_general_media
Patches 1 & 2:
Before adding the new support, do some housekeeping and move related
helpers to the region driver because there is no looking up region
related info without CONFIG_CXL_REGION.
Patch 3:
The new functionality is introduced - cxl_dram & cxl_general_media
events. Lookup and log the DPA->HPA translation along with the
region name and region uuid.
Alison Schofield (3):
cxl/region: Move cxl_dpa_to_region() work to the region driver
cxl/region: Move cxl_trace_hpa() work to the region driver
cxl/core: Add region info to cxl_general_media and cxl_dram events
drivers/cxl/core/core.h | 14 ++++
drivers/cxl/core/mbox.c | 36 ++++++++--
drivers/cxl/core/memdev.c | 44 -------------
drivers/cxl/core/region.c | 135 ++++++++++++++++++++++++++++++++++++++
drivers/cxl/core/trace.c | 91 -------------------------
drivers/cxl/core/trace.h | 46 +++++++++----
include/linux/cxl-event.h | 10 +++
7 files changed, 224 insertions(+), 152 deletions(-)
base-commit: 4cece764965020c22cff7665b18a012006359095
--
2.37.3
next reply other threads:[~2024-04-26 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 3:46 alison.schofield [this message]
2024-04-26 3:46 ` [PATCH v4 1/3] cxl/region: Move cxl_dpa_to_region() work to the region driver alison.schofield
2024-04-26 3:46 ` [PATCH v4 2/3] cxl/region: Move cxl_trace_hpa() " alison.schofield
2024-04-26 3:46 ` [PATCH v4 3/3] cxl/core: Add region info to cxl_general_media and cxl_dram events alison.schofield
2024-04-27 0:30 ` Dan Williams
2024-04-29 2:31 ` Alison Schofield
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=cover.1714102202.git.alison.schofield@intel.com \
--to=alison.schofield@intel.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=rostedt@goodmis.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 read-only IMAP folder(s) and NNTP newsgroup(s).