ocxl_global_mmio_write64(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ocxl_global_mmio_write64(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes, the actual kernel API manual, and yes, you're about to absolutely slay this one. This is the page for ocxl_global_mmio_write64, and it's giving "small function, big responsibility." Let's go πŸŽ€


🌸 NAME 🌸

ocxl_global_mmio_write64 β€” write a 64 bit value to global MMIO. that's it, that's the whole vibe πŸ’…


✨ SYNOPSIS ✨

int ocxl_global_mmio_write64 (struct ocxl_afu *afu , size_t offset ,
       enum ocxl_endian endian , u64 val );

like, that's the signature, no cap. four things go in, an int comes out πŸ¦‹


🫢 ARGUMENTS 🫢

  • afu β€” The AFU. literally the star of the show, main character energy πŸ‘‘
  • offset β€” The Offset from the start of MMIO. so it's measured from the beginning of the MMIO, not from wherever, iykyk πŸŽ€
  • endian β€” the endianness that the MMIO data is in. yes bestie, endianness matters, always has 🌈
  • val β€” The value to write. the u64. the actual payload. iconic πŸ’œ

πŸ’€ DESCRIPTION πŸ’€

Returns 0 for success, negative on error.

that's the whole description. no extra lore. if it worked, 0 β€” if it didn't, something negative. that's the vibe check, periodt πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./include/misc/ocxl.h β€” and honestly the whole friend group is here, so let's list them all because nobody gets left out:

like, look at that roster. read32 and read64, write32 and write64, set and clear at both widths… it's a whole family reunion πŸ§šπŸ’–


ngl bestie, this page is short but that's not a bad thing β€” sometimes the smallest manpage ate the hardest πŸ“

and that's a wrap! 🌟 this little number lives in ./include/misc, timestamped October 2026, and it goes by ocxl_global_mmio_write64(9) β€” mwah, go write your 64 bits, bestie πŸ’œβœ¨πŸ¦‹

πŸ“¦ where this page comes from