vfio_ap_mdev_set_kvm(9)

💅 NAME 💅

vfio_ap_mdev_set_kvm — okay so bestie, this one sets all the data for @matrix_mdev that's needed to manage AP resources for the guest whose state is represented by @kvm. Literally all of it. No crumbs left. 👑

---

✨ SYNOPSIS ✨

int vfio_ap_mdev_set_kvm (struct ap_matrix_mdev *matrix_mdev , struct
kvm *kvm );

---

🎀 ARGUMENTS 🎀

• matrix_mdev — a mediated matrix device. that's the one we're setting stuff on, she's the main character here 🫶
• kvm — reference to a KVM instance. the guest's whole vibe, basically 🌸

---

🔥 RETURN 🔥

Returns 0 if no other mediated matrix device has a reference to kvm. Otherwise it returns an -EPERM — like, nope, another mdev already claimed her, soz 💀

---

🦋 SEE ALSO 🦋

The kernel file this lives in, no cap:

./drivers/s390/crypto/vfio_ap_ops.c

And the whole friend group, fr fr:

• get_update_locks_for_kvm(9)
• release_update_locks_for_kvm(9)
• get_update_locks_for_mdev(9)
• release_update_locks_for_mdev(9)
• get_update_locks_by_apqn(9)
• get_update_locks_for_queue(9)
• vfio_ap_mdev_get_queue(9)
• vfio_ap_wait_for_irqclear(9)
• vfio_ap_free_aqic_resources(9)
• vfio_ap_irq_disable(9)
• vfio_ap_validate_nib(9)
• ensure_nib_shared(9)
• vfio_ap_irq_enable(9)
• vfio_ap_le_guid_to_be_uuid(9)
• handle_pqap(9)
• vfio_ap_mdev_verify_no_sharing(9)
• vfio_ap_mdev_validate_masks(9)
• assign_adapter_store(9)
• vfio_ap_mdev_unlink_adapter(9)
• unassign_adapter_store(9)
• assign_domain_store(9)
• unassign_domain_store(9)
• assign_control_domain_store(9)
• unassign_control_domain_store(9)
• vfio_ap_mdev_unset_kvm(9)
• vfio_ap_mdev_resource_in_use(9)
• vfio_ap_mdev_hot_unplug_cfg(9)
• vfio_ap_mdev_cfg_remove(9)
• vfio_ap_mdev_on_cfg_remove(9)
• vfio_ap_filter_apid_by_qtype(9)
• vfio_ap_mdev_cfg_add(9)
• vfio_ap_mdev_on_cfg_add(9)
• vfio_ap_on_cfg_changed(9)

---

That's the whole lore, bestie — brought to you by Kernel API Manual, source living pretty in ./drivers/s390/crypto, dated October 2026. go off, vfio_ap_mdev_set_kvm(9) iconique behavior only 💖✨🎀