hcall_inject_msi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hcall_inject_msi(9) πŸ’…

okay so bestie, welcome to the hcall_inject_msi(9) page from the Kernel API Manual β€” we're keeping it cute, and we're keeping every detail. 🫢✨


🌸 NAME 🌸

hcall_inject_msi β€” deliver a MSI interrupt to a User VM. That's the vibe: one hypercall, one MSI interrupt, one User VM on the receiving end. πŸ’Œ


πŸ’– SYNOPSIS πŸ’–

the signature is giving exactly this, character for character:

long hcall_inject_msi (u64 vmid , u64 msi );

πŸŽ€ ARGUMENTS πŸŽ€

  • vmid β€” User VM ID. This is the ID of the User VM you're aiming at 🎯.
  • msi β€” Service VM GPA of MSI message. That's the literal value you pass, no cap πŸ’….

πŸ”₯ RETURN πŸ”₯

0 on success, <0 on failure. So yeah: success is 0 βœ…, failure is less than 0 😭. That's the whole return situation.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/virt/acrn/hypercall.h, plus the whole hypercall friend group:


okay bye bestie β€” this page comes from ./drivers/virt/acrn, stamped October 2026, and it's absolutely the hcall_inject_msi(9) page πŸ’…βœ¨

πŸ“¦ where this page comes from