Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates for kernel changes in CXL trace error events #178

Closed
wants to merge 3 commits into from

Conversation

shijujose4
Copy link
Contributor

  1. rasdaemon: CXL: Fix uncorrectable macro spelling
  2. rasdaemon: CXL: Extract, log and record region info from cxl_general_media and cxl_dram events
  3. rasdaemon: ras-mc-ctl: Log hpa and region info from cxl_general_media and cxl_dram tables

Fix the macro (CXL_GMER_EVT_DESC_UNCORECTABLE_EVENT) spelling .
Uncorrectable is spelled with two r's.

Signed-off-by: Shiju Jose <[email protected]>
…media and cxl_dram events

Add extract, log and record region info to cxl_general_media and
cxl_dram events.

The corresponding kernel changes:
https://lore.kernel.org/all/[email protected]/T/#m6fd773b5477fc44b875848e053708a1c8996c4e4

Signed-off-by: Shiju Jose <[email protected]>
… and cxl_dram tables

Add support for read and log hpa and region info from cxl_general_media and
cxl_dram tables.

Note: This change does not have backward compatability, because
the select command with newly added columns would fail with previous
CXL tables where newly added columns are not present.
The issue can be solved with updating the CXL table's name to v2,
but again no backward compatability in ras-mc-ctl for listing errors
which fails when previous version of CXL table only present in the
database as it cannot find v2 of the table.

Signed-off-by: Shiju Jose <[email protected]>
@mchehab
Copy link
Owner

mchehab commented Nov 18, 2024

Merged, thanks!

@mchehab mchehab closed this Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants