Skip to content

Comments

OCP Persistent Event Log Parsing Support#3089

Merged
igaw merged 2 commits intolinux-nvme:masterfrom
brandon-paupore-sndk:ocp-pel-supp
Feb 10, 2026
Merged

OCP Persistent Event Log Parsing Support#3089
igaw merged 2 commits intolinux-nvme:masterfrom
brandon-paupore-sndk:ocp-pel-supp

Conversation

@brandon-paupore-sndk
Copy link
Contributor

This set of changes introduces a new OCP plugin command that mirrors the base nvme persistent-event-log command, but has additional parsing for the OCP 2.5 TCG Activity Event data.

The first commit here reworks the current PE log parsing to expose the bulk of it in the nvme_print header file, such that reusing those functions doesn't require duplicating all of that logic in a plugin for handling Vendor Specific events. Let me know if this would be preferred to be left alone or pulled out into a separate Jira, but avoiding some duplication here seems worthwhile.

This allows for any plugin to more easily parse Persistent Event log
data without requiring that the various event parsing functions be
copied into the plugin. This then allows for more specific handling of
Vendor Specific Information associated with any event or for any Vendor
Specific Events.

Signed-off-by: Brandon Paupore <brandon.paupore@sandisk.com>
Reviewed-by: Jeffrey Lien <jeff.lien@sandisk.com>
This introduces a new OCP plugin command that mirrors the base nvme
persistent-event-log command, but has additional parsing for the OCP 2.5
TCG Activity Event data.

Signed-off-by: Brandon Paupore <brandon.paupore@sandisk.com>
Reviewed-by: Jeffrey Lien <jeff.lien@sandisk.com>
@igaw igaw merged commit 406f50a into linux-nvme:master Feb 10, 2026
20 of 21 checks passed
@igaw
Copy link
Collaborator

igaw commented Feb 10, 2026

Thanks!

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