ocxl_afu_set_private(9)
β¨ ocxl_afu_set_private β¨
okay so bestie, we're in the kernel API manual today β this one lives in section 9, and it's all about giving an OpenCAPI AFU some opaque hardware specific information. iykyk π
π«Ά SYNOPSIS
void ocxl_afu_set_private (struct ocxl_afu *afu , void *private );
literally that's it. a void return, two arguments, no drama. periodt. β¨
π ARGUMENTS
afuβ the OpenCAPI AFU. that's the main character of this whole function ngl πprivateβ the opaque hardware specific information you're assigning to the driver. it's opaque, bestie, meaning it's not our business to peek inside β we just hand it over π
π₯ SEE ALSO
the kernel file ./include/misc/ocxl.h is your bestie here, plus this whole girl squad of related calls:
ocxl_function_open(9)ocxl_function_afu_list(9)ocxl_function_fetch_afu(9)ocxl_afu_get(9)ocxl_afu_put(9)ocxl_function_config(9)ocxl_function_close(9)ocxl_context_alloc(9)ocxl_context_free(9)ocxl_context_attach(9)ocxl_context_detach(9)ocxl_afu_irq_alloc(9)ocxl_afu_irq_free(9)ocxl_afu_irq_get_addr(9)ocxl_irq_set_handler(9)ocxl_afu_config(9)ocxl_afu_get_private(9)ocxl_global_mmio_read32(9)ocxl_global_mmio_read64(9)ocxl_global_mmio_write32(9)ocxl_global_mmio_write64(9)ocxl_global_mmio_set32(9)ocxl_global_mmio_set64(9)ocxl_global_mmio_clear32(9)ocxl_global_mmio_clear64(9)
like, go read them all, they're iconic π
ngl there's no NAME section body beyond the one-liner above, no DESCRIPTION, no OPTIONS, no RETURN VALUE, no ERRORS, no warnings and no bugs listed here β this page is short and sweet and we're not gonna invent lore that isn't in the source π
πΈ and that's the whole vibe! this page ships out of ./include/misc, October 2026 edition, signed off under the section 9 name ocxl_afu_set_private β slay, go set some private, bestie π¦π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms