Skip to content

fix(pcie Issue#224): handle unknown PCIe capability IDs without crashing#225

Open
cijohnson wants to merge 1 commit into
amd:developmentfrom
cijohnson:ichristo/pcie-collector-fix
Open

fix(pcie Issue#224): handle unknown PCIe capability IDs without crashing#225
cijohnson wants to merge 1 commit into
amd:developmentfrom
cijohnson:ichristo/pcie-collector-fix

Conversation

@cijohnson

Copy link
Copy Markdown

The PCIe collector raised an unhandled ValueError when the config space exposed a capability ID not modeled in CapabilityEnum / ExtendedCapabilityEnum (e.g. 0x2F / IDE on MI300X), aborting the entire PCIe plugin run.

  • Add ExtendedCapabilityEnum.IDE = 0x2F (Integrity and Data Encryption)
  • Guard the enum conversion in get_cap_cfg so any unknown cap id is skipped with a warning instead of taking down the whole collection.

Fixes #224

Summary

Test plan

  • pytest test/unit
  • pytest test/functional (if applicable)
  • pre-commit run --all-files

Checklist

  • Added/updated tests (or explained why not)
  • Updated docs/README if behavior changed
  • No secrets or credentials committed

The PCIe collector raised an unhandled ValueError when the config space
exposed a capability ID not modeled in CapabilityEnum / ExtendedCapabilityEnum
(e.g. 0x2F / IDE on MI300X), aborting the entire PCIe plugin run.

- Add ExtendedCapabilityEnum.IDE = 0x2F (Integrity and Data Encryption)
- Guard the enum conversion in get_cap_cfg so any unknown cap id is skipped
  with a warning instead of taking down the whole collection.

Fixes amd#224

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

[Bug]: PCIe collector crashes on unknown ExtendedCapabilityEnum value (e.g. 0x2F / IDE)

1 participant