vfio_ap_mdev...ource_in_use(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vfio_ap_mdev_resource_in_use β€” bestie edition πŸŽ€

okay so this page lives in the Kernel API Manual (yes, that's the manual name, it's giving very official ✨), and the function we're stanning today is vfio_ap_mdev_resource_in_use. The header up top gets all shy and truncates it to vfio_ap_mdev...ource_in_use(9) β€” iconic of it, honestly, but the NAME section has the full thing.


🌸 NAME 🌸

vfio_ap_mdev_resource_in_use β€” literally just checks whether any of a set of APQNs is assigned to a mediated device under the control of the vfio_ap device driver. That's it. That's the whole gig. A little vibe check for your APQNs 🫢


✨ SYNOPSIS ✨

int vfio_ap_mdev_resource_in_use (unsigned long *apm , unsigned long
*aqm );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • apm β€” a bitmap specifying a set of APIDs comprising the APQNs to check. bitmappie behavior πŸ’…
  • aqm β€” a bitmap specifying a set of APQIs comprising the APQNs to check. the other half of the APQN duo 🫢

πŸ’– RETURN πŸ’–

  • -EADDRINUSE if one or more of the APQNs specified via apm/aqm are assigned to a mediated device under the control of the vfio_ap device driver. (translation: something's already occupying the spot, no cap 😭)
  • Otherwise, return 0. clean slate, we love to see it ✨

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/s390/crypto/vfio_ap_ops.c β€” the mothership, iykyk πŸ‘‘

and also the whole friend group:


ngl the whole s390 crypto squad is in that list, so if you're going down this rabbit hole, hydrate first πŸ’§

and that's the page, bestie πŸ’œ β€” brought to you by ./drivers/s390/crypto, dated October 2026, and printed with love by the vfio_ap_mdev...ource_in_use(9) crew. periodt. πŸ’…πŸŒ·

πŸ“¦ where this page comes from