hgcm_call_preprocess(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– hgcm_call_preprocess β€” the kernel API manual page, bestie edition πŸ’–

Okay so we're doing hgcm_call_preprocess(9) today β€” it's a section 9 kernel API page, the kind that lives down in ./drivers/virt/vboxguest, and honestly? It's giving prep work. It's the function that rolls up its sleeves before the actual HGCM call happens. πŸŽ€

✨ NAME ✨

hgcm_call_preprocess β€” it preprocesses the HGCM call, no cap. That means it validates the parameters, allocates the bounce buffers, and figures out how much extra storage we need for the page lists. Three jobs, one function, main character energy fr fr. πŸ’…

🌸 SYNOPSIS 🌸

int hgcm_call_preprocess (const struct vmmdev_hgcm_function_parameter
*src_parm , u32 parm_count , void ***bounce_bufs_ret , size_t *extra );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • src_parm β€” a pointer to the source function call parameters. Like, the original ones, before anything gets touched. 🫢
  • parm_count β€” the number of function call parameters. Count 'em, bestie. ✨
  • bounce_bufs_ret β€” where to return the allocated bouncebuffer array. Yeah, the triple-pointer. It's a lot. It's iconic. Don't question it. 😭
  • extra β€” where to return the extra request space needed for physical page lists. This is the "how much more room do we need" out-parameter. πŸ“¦

πŸ”₯ RETURN πŸ”₯

0 or a negative errno value. That's it, that's the whole vibe check β€” zero means slay, negative means something went sideways. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page!! ⭐ this lil beauty comes from ./drivers/virt/vboxguest, it's dated October 2026, and it's filed under hgcm_call_preprocess(9). mwah, go preprocess something πŸ’œπŸ“

πŸ“¦ where this page comes from