tdx_mcall_get_report0(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is the tdx_mcall_get_report0(9) page from the Kernel API Manual β€” manual name folded in right here, bestie β€” and tdx_mcall_get_report0 is literally the wrapper to get TDREPORT0 (a.k.a. TDREPORT subtype 0) using the TDG.MR.REPORT TDCALL. slay. πŸ’…


✨ SYNOPSIS ✨

int tdx_mcall_get_report0 (u8 *reportdata , u8 *tdreport );

πŸŽ€ ARGUMENTS πŸŽ€

  • reportdata β€” address of the input buffer which contains user-defined REPORTDATA to be included into TDREPORT. It's giving "here's the data" slot, bestie. ✨
  • tdreport β€” address of the output buffer to store TDREPORT. This is where the result lands. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

Refer to the section titled "TDG.MR.REPORT leaf" in the TDX Module v1.0 specification for more information on the TDG.MR.REPORT TDCALL. iykyk, the spec has the deets. πŸ“–

It is used in the TDX guest driver module to get the TDREPORT0. no cap.

Return 0 on success, -ENXIO for invalid operands, -EBUSY for busy operation, or -EIO on other TDCALL failures. periodt. πŸ’…


πŸ’… SEE ALSO πŸ’…

The SEE ALSO besties are:


cute sign-off: source/version ./arch/x86/coco/tdx, date October 2026, page tdx_mcall_get_report0(9). stay iconic, bestie πŸ«ΆπŸ¦‹

πŸ“¦ where this page comes from