hcall_inject_msi(9)
π 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:
hcall_sos_remove_cpu(9)hcall_create_vm(9)hcall_start_vm(9)hcall_pause_vm(9)hcall_destroy_vm(9)hcall_reset_vm(9)hcall_set_vcpu_regs(9)hcall_vm_intr_monitor(9)hcall_set_irqline(9)hcall_set_ioreq_buffer(9)hcall_notify_req_finish(9)hcall_set_memory_regions(9)hcall_create_vdev(9)hcall_destroy_vdev(9)hcall_assign_mmiodev(9)hcall_deassign_mmiodev(9)hcall_assign_pcidev(9)hcall_deassign_pcidev(9)hcall_set_ptdev_intr(9)hcall_reset_ptdev_intr(9)
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
- 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