hgcm_call_init_call(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hgcm_call_init_call(9) β€” Kernel API Manual πŸŽ€

okay bestie, welcome to hgcm_call_init_call from the Kernel API Manual β€” this is the one that sets up the call request we're shipping off to the host πŸ‘‘ no cap.


✨ NAME ✨

hgcm_call_init_call β€” Initializes the call request that we're sending to the host. literally that's her whole job πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

void hgcm_call_init_call (struct vmmdev_hgcm_call *call , u32 client_id
, u32 function , const struct vmmdev_hgcm_function_parameter *src_parm ,
u32 parm_count , void **bounce_bufs );

🌸 ARGUMENTS 🌸

okay so here's the whole cast, main character energy only ✨

  • call β€” The call to initialize. this is the baby you're setting up 🫢
  • client_id β€” The client ID of the caller. gotta know who's calling, iykyk πŸ’…
  • function β€” The function number of the function to call. yes it's very "function number of the function", the kernel said what it said πŸ’€
  • src_parm β€” Pointer to source function call parameters. the source deets πŸ“
  • parm_count β€” Number of function call parameters. how many of the little guys there are πŸ”₯
  • bounce_bufs β€” The bouncebuffer array. iconic name, no notes πŸŽ€

πŸ‘€ SEE ALSO πŸ‘€


bestie fr fr go read the SEE ALSO list, it's giving required reading πŸ“šβœ¨

that's the whole page, mwah πŸ’‹ β€” brought to you by ./drivers/virt/vboxguest, dated October 2026, and the very page you just read, hgcm_call_init_call(9) πŸŒˆβ­πŸ’œ

πŸ“¦ where this page comes from