LINUX PCIe & DMA · SPEC-AWARE INVESTIGATION
Your spec.
Your registers.Your next check.
Turn a hardware specification and a failing capture into a useful next check.
deserve attention?A clue you can inspect.
01 / START WITH THE RIGHT SPEC
A dense document.
A clearer starting point.
Start with a source-linked QDMA field map. Import your queue capture, or explore three examples without hardware.
Software Descriptor Context
Selected fields · 256-bit H2C queue context · internal MM
02 / MAKE THE BITS MAKE SENSE
Meet your field map.
Click a field to see its meaning and its place in the context.
Compare a working queue with a stalled sample.
| Field / bits | Meaning | Working | Capture |
|---|
No matching fields. Try a name such as irq_arm or choose Selected fields.
03 / FOLLOW THE EVIDENCE
The bits tell a more useful story.
THE SERVICE BEHIND THE DEMO
A better starting point.
Every time it happens.
Keep the spec, the working state and the investigation together.
Private projects · preview Separate workspace for supported prepared QDMA investigation exports. Typed maps here stay local.Understand this capture.
Import supported queue captures, compare the bits and export the evidence.
Use the current capture toolBuild your team’s memory.
Private device libraries, working baselines and reusable checks.
What is real in this demo?
The selected field definitions are curated from AMD’s public PG302 v4.0 guide. The bit decoder, supported JSON import, comparison, filters and downloads run in your browser. Examples are synthetic; imported capture metadata is user supplied and is not independently verified. Real input requires the supported QDMA 4.0 H2C internal MM context, device/queue identity, timestamp and provenance. This is a selected field map, not a complete device register map. Local PDF text extraction produces editable, unverified candidate rows with source pages and a file fingerprint. Scanned/image PDFs and OCR are unsupported. Reviewed PDF rows can become a typed map only after an explicit device/address-space, revision, byte/word-order and register-width review. Matching user-supplied snapshots can then be decoded and compared locally; no hardware access is performed. A separate private-project preview saves supported QDMA investigation exports only after explicit upload consent. Typed maps and PDFs here remain local. AI explanations, shared device libraries and live hardware access remain unimplemented.
A queue context alone does not establish DMA mappings, PCIe transactions, completion delivery or the original cause of a stall. Missing evidence stays unknown.