ibmvtpm_crq_get_rtce_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ibmvtpm_crq_get_rtce_size β€” the Kernel API Manual era πŸ’–

okay so bestie, welcome to the <pink>ibmvtpm_crq_get_rtce_size(9)</pink> page, like the actual kernel API manual for this one little function, and honestly? she's short but she's serving. we're in the ibmvtpm cinematic universe today and this is THE function that slides into the CRQ and asks for the rtce size. main character behavior fr fr πŸŽ€


✨ NAME ✨

ibmvtpm_crq_get_rtce_size β€” send a CRQ request to get the rtce size πŸ’… that's literally it, that's the whole job, she asks and she receives, no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

int ibmvtpm_crq_get_rtce_size (struct ibmvtpm_dev *ibmvtpm );

like, one function, one argument, one vibe. copy it exactly bestie, the spacing in there is canon 🫢


🌸 ARGUMENTS 🌸

  • ibmvtpm β€” the vtpm device struct πŸ’– this is the whole entire vtpm situation being passed in, she's the one our function is gonna talk to. the way that struct just has to show up and be a device… obsessed.

⭐ RETURN ⭐

  • 0 on success β€” slay, we ate, everything worked ✨
  • Non-zero on failure β€” 😭 the non-zero branch said "not today" and honestly we respect the honesty. non-zero bad, 0 good, that's the whole mood.
ngl this is the entire return contract and there's no in-between, so check your return value bestie, don't just assume it's giving success πŸ’€

πŸ’œ SEE ALSO πŸ’œ

the whole friend group, the entire group chat, the kernel file AND the squad of sibling functions, all of them, no one left out 🧚

like literally all of them, iykyk 🌈


and that's the page!! source/version situation for the sign-off: this one's filed under ./drivers/char/tpm, dated October 2026, and it's ibmvtpm_crq_get_rtce_size(9) through and through. periodt πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from