RFC CXL: Read and clear event logs
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest9 patches 41 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | cxl/mem: Implement Get Event Records commandMAINTAINERS drivers/ drivers/ +2 more | +255 | 15 replies | |
| 2/9 | cxl/mem: Implement Clear Event Records commanddrivers/ drivers/ include/ | +44 | 2 replies | |
| 3/9 | cxl/mem: Clear events on driver loaddrivers/ tools/ | +4 | 1 reply | |
| 4/9 | cxl/mem: Trace General Media Event Recorddrivers/ drivers/ include/ | +172 | 3 replies | |
| 5/9 | cxl/mem: Trace DRAM Event Recorddrivers/ drivers/ include/ | +154 | 3 replies | |
| 6/9 | cxl/mem: Trace Memory Module Event Recorddrivers/ drivers/ include/ | +196 | 3 replies | |
| 7/9 | cxl/test: Add generic mock eventstools/ | +291 | 7 replies | |
| 8/9 | cxl/test: Add specific eventstools/ | +70 | 1 reply | |
| 9/9 | cxl/test: Simulate event log overflowtools/ | +36 | 1 reply |
Reviews trailers per patch
1 of 9 patches has a Reviewed-by or Acked-by.
| Patch | Jonathan Cameron |
|---|---|
| 1/9 | |
| 2/9 | R-b |
| 3/9 | |
| 4/9 | |
| 5/9 | |
| 6/9 | |
| 7/9 | |
| 8/9 | |
| 9/9 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH 0/9] CXL: Read and clear event logs
From: Ira Weiny <[email protected]>
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 events.
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
MAINTAINERS | 1 + 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
Signature · 1 line
2.35.3