[lkml]   [2022]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH 0/9] CXL: Read and clear event logs
From: Ira Weiny <>

Event records inform the OS of various device events. Events are not needed
for any kernel operation but various user level software will want to track

Add event reporting through the trace event mechanism. On driver load read and
clear all device events.

Normally interrupts will trigger new events to be reported as they occur.
Because the interrupt code is still being worked on this series provides a
cxl-test mechanism to create a series of events and trigger the reporting of
those events.

This series is submitted as an RFC for a few reasons:

1) Interrupt support is still missing
2) I'd like to get comments on the format of the trace events
3) Some of the event formats are badly aligned and I would like to see
if there is any clarification on how the data will be formatted
(See individual patches for details)

Ira Weiny (9):
cxl/mem: Implement Get Event Records command
cxl/mem: Implement Clear Event Records command
cxl/mem: Clear events on driver load
cxl/mem: Trace General Media Event Record
cxl/mem: Trace DRAM Event Record
cxl/mem: Trace Memory Module Event Record
cxl/test: Add generic mock events
cxl/test: Add specific events
cxl/test: Simulate event log overflow

drivers/cxl/core/mbox.c | 143 ++++++++
drivers/cxl/cxlmem.h | 149 +++++++++
drivers/cxl/pci.c | 2 +
include/trace/events/cxl-events.h | 521 ++++++++++++++++++++++++++++++
include/uapi/linux/cxl_mem.h | 2 +
tools/testing/cxl/test/mem.c | 399 +++++++++++++++++++++++
7 files changed, 1217 insertions(+)
create mode 100644 include/trace/events/cxl-events.h

base-commit: 1cd8a2537eb07751d405ab7e2223f20338a90506

 \ /
  Last update: 2022-08-13 07:33    [W:0.348 / U:0.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site