assign_control_domain_store(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ assign_control_domain_store(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual page for assign_control_domain_store(9) β€” yes, the manual name is right there near the top, because we are organized and iconic like that πŸ’…βœ¨


🌸 NAME 🌸

assign_control_domain_store β€” parses the domain ID from @buf and sets the corresponding bit in the mediated matrix device's ADM. that's the assignment vibe, no cap πŸ¦‹

✨ SYNOPSIS ✨

       ssize_t assign_control_domain_store (struct device *dev , struct
       device_attribute *attr , const char *buf , size_t count );

πŸ’… ARGUMENTS πŸ’…

  • dev β€” the matrix device. main character energy tbh πŸ‘‘
  • attr β€” the mediated matrix device's assign_control_domain attribute. yes, that whole attribute situation ✨
  • buf β€” a buffer containing the domain ID to be assigned. the ID lives here, bestie πŸ“¦
  • count β€” the number of bytes in buf. byte-counting queen behavior πŸ”’

πŸŽ€ RETURN πŸŽ€

on success it gives you the number of bytes processed β€” but only if the domain ID is valid. otherwise, it returns one of the following errors:

  • -EINVAL β€” the ID is not a number πŸ’€
  • -ENODEV β€” the ID exceeds the maximum value configured for the system 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/s390/crypto/vfio_ap_ops.c

these related pages are the friend group, go say hi 🫢

mwah πŸ’‹ source/version + date sign-off: ./drivers/s390/crypto, dated October 2026, for assign_control_domain_store(9). that's the whole page, bestie β€” slay and stay safe 🌈🫢

πŸ“¦ where this page comes from