feat: add PCI subsystem IDs to GPU fingerprints - #235
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe change adds subsystem PCI identifiers to ChangesGPU hardware fingerprinting
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The daemon now captures PCI subsystem IDs and logs deterministic GPU hardware fingerprints without changing GPU construction behavior. No concrete merge-blocking risk remains. Sequence Diagram(s)sequenceDiagram
participant Sysfs
participant PciDiscovery
participant PciDevice
participant GpuEnumerator
Sysfs->>PciDiscovery: Read subsystem PCI identifiers
PciDiscovery->>PciDevice: Construct device with identifiers
PciDevice-->>GpuEnumerator: Provide hardware fingerprint
GpuEnumerator->>GpuEnumerator: Log PCI address and fingerprint
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
luytan
left a comment
There was a problem hiding this comment.
Postponed until we find a truly unique ID
Description
This change adds PCI subsystem vendor and device IDs to the internal PCI model. For this the daemon reads both values from sysfs during IOMMU and normal PCI enumeration. Then the GPU enumeration logs a deterministic hardware fingerprint for POC debugging.
Related to #228
TODO for future PRs related to #228
gpu_state.json.Checklist: