STRUCT KHO_BLOCK_HEADER_SER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct kho_block_header_ser(9) β€” Kernel API Manual πŸ’–

okay so bestie, we're looking at struct kho_block_header_ser, and lowkey it's the little header that could. it lives in the Kernel API Manual and it's giving "small but crucial" main character energy. let's get into it 🫢


✨ NAME ✨

struct kho_block_header_ser β€” the header for the serialized data block. yes, that's literally its whole job, and it does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

struct kho_block_header_ser {
    u64 next;
    u64 count;
};

that's the whole struct. two u64s. no cap, that's it. iconic minimalism ✨


πŸŽ€ Members πŸŽ€

  • next β€” the physical address of the next struct kho_block_header_ser. yup, it points at its sibling. it's a chain, bestie πŸ”—
  • count β€” the number of entries that immediately follow this header in the memory block. so like, "how many friends am i bringing to the function" energy πŸ“

πŸ¦‹ Description πŸ¦‹

so picture this: this structure is located at the very beginning of a block of physical memory that's preserved across a kexec. main character placement fr fr πŸ‘‘

and what does it do? it provides the necessary metadata to interpret the array of entries that follow it. basically it's the translator, the vibes-checker, the "here's how you read the rest of this block" note. without it the entries are just… noise 😭


πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./include/linux/kho/abi/block.h
  • KHO Serialization Blocks ABI(9)
  • KHO_BLOCK_SIZE(9)

πŸ’œ quick vibe check: next is a physical address, not some virtual thing β€” don't come for me, that's straight from the source πŸ™ˆ

and that's the whole page, bestie! this one's from ./include/linux/kho/abi, dated October 2026 β€” go forth and interpret those entries correctly πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from