STRUCT OCS_HCU_IDATA(9)

💖 struct ocs_hcu_idata(9) 💖

okay so this is a page from the Kernel API Manual, and it's literally all about struct ocs_hcu_idata — the intermediate data that the HCU generates. yes bestie, the HCU. lowercase king of "i made some data and it's in between states". we love a middle child. 🎀

✨ NAME ✨

struct ocs_hcu_idata — the intermediate data generated by the HCU. that's it, that's the whole vibe. 👑

🦋 SYNOPSIS 🦋

struct ocs_hcu_idata {
    u32 msg_len_lo;
    u32 msg_len_hi;
    u8 digest[SHA512_DIGEST_SIZE];
 };

look at her. three whole members. she's compact, she's iconic, she's ready to hold your lengths and your digest at the same time. no cap. 💅

🌸 Members 🌸

• msg_len_lo — the length of the data the HCU has operated on, in bits, low 32b. that's the bottom half of the number, fr fr. 🍓
• msg_len_hi — the length of the data the HCU has operated on, in bits, high 32b. and that's the top half. together they're giving "64-bit length, split clean". 🫶
• digest — the digest read from the HCU. now LISTEN, because this is the important part:
  • if the HCU is terminated, it will contain the actual hash digest ✨
  • otherwise? it's the intermediate state. mid-hash. still cooking. 🧚

ngl the digest field is doing double duty and that's lowkey iconic of her, but don't get it twisted — terminated means real digest, not-terminated means intermediate state. that distinction is the whole point, iykyk. 💀

🌈 SEE ALSO 🌈

go look at the kernel file ./drivers/crypto/intel/keembay/ocs-hcu.h — that's where the lore lives. also check out struct ocs_hcu_dev(9) and struct ocs_hcu_hash_ctx(9) because they're her besties and they show up in the same group chat. 💜

mwah 💋 that's the page!! it lives in ./drivers/crypto/intel/keembay, it's dated October 2026, and it came to you courtesy of the Kernel API Manual. go read your structs, bestie, and slay responsibly. 🎀✨🔥