libnvme(9)

💖 NAME 💖

Okay bestie, welcome to the libnvme(9) page 🎀. This one is all about struct nvme_tdisp_device_interface_report — the NVMe TDISP DEVICE_INTERFACE_REPORT Reporting Structure. Yes, that is a whole mouthful, and yes, we are going to decode it together 💅✨.

✨ SYNOPSIS ✨

       struct nvme_tdisp_device_interface_report {
           __le32 tni;
           __le32 ti;
           __u8 cu;
           __u8 vu;
           __u8 rsvd10[2];
           __le32 aqv;
           __le32 asv;
           __le32 acv;
           __le32 cv;
           __le32 pmv;
           __le32 pcv;
           __u8 qh[48];
           __u8 rsvd84[44];
        };

🧚 Members 🧚

• tni — TDISP NVMe Identifier, and it shall be NVME_TDISP_NVME_IDENTIFIER. Periodt 💅.
• ti — TDISP Information, see enum nvme_tdisp_ti. Go peek at the enum, iykyk 👀.
• cu — CSVL Used: the Controller State Version Index of the NVMe Controller State data structure used to generate qh. Very main character bookkeeping energy ✨.
• vu — VER Used: the Version field in the NVMe Controller State data structure used to generate qh. Matching vibes with cu, fr fr 🦋.
• rsvd10 — Reserved. Nothing to see here, bestie 🙈.
• aqv — AQA Value. That's the whole tea ☕.
• asv — ASQ Value. Noted and slaying 💖.
• acv — ACQ Value. Also noted 👑.
• cv — CMBMSC Value. Yup, exactly that 💫.
• pmv — PMRMSC Value. Keep it moving 🌸.
• pcv — PMRCTL Value. Iconic little field name 🎀.
• qh — Queue Hash: a SHA-384 hash of all the fields in the NVMe Controller State data structure, see struct nvme_lm_controller_state_data. Obsessed with a good hash, ngl 🔥.
• rsvd84 — Reserved. More padding, more chill 😌.

🌈 Description 🌈

So picture this 🫶: this struct is the NVMe class-specific DEVICE_SPECIFIC_INFO payload that a PCIe Function returns in response to a PCIe TDISP GET_DEVICE_INTERFACE_REPORT request — refer to the NVM Express over PCIe Transport Specification for the full lore 📚.

And no cap: there is no NVMe Admin, I/O, or MI command that transfers this structure. It is produced by the device's Device Security Module and consumed by a platform TEE Security Module entirely via the PCIe TDISP protocol, outside of any NVMe command/response mechanism. The way that this type is provided is purely so that software which has otherwise obtained a DEVICE_INTERFACE_REPORT (e.g., from a TDISP/SPDM stack) can decode its NVMe-specific portion. It's giving "decoder helper with zero NVMe command drama," and honestly? We respect it 💜.

That's the whole page, bestie 🫶. Source/version tea: this is libnvme(9) from the API Manual, the page is struct nvme_tdisp_device_interface_report, and the date at the very end is October 2026 ✨💋.