__ap_send(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to __ap_send from the Kernel API Manual. Its whole entire job is literally: Send message to adjunct processor queue. That’s the vibe, no cap 🫢


✨ SYNOPSIS ✨

struct ap_queue_status __ap_send (ap_qid_t qid , unsigned long psmid ,
       void *msg , size_t msglen , int special );

πŸŽ€ ARGUMENTS πŸŽ€

  • qid β€” The AP queue number. iconic little queue ID, we love her πŸ’…
  • psmid β€” The program supplied message identifier.
  • msg β€” The message text. the actual message, bestie ✨
  • msglen β€” The message length.
  • special β€” Special Bit. capital S, capital B, respect it πŸŽ€

πŸ”₯ DESCRIPTION πŸ”₯

Returns AP queue status structure. That’s the returned goodie πŸ¦‹

Condition code 1 on NQAP can’t happen because the L bit is 1. literally cannot happen, the L bit said no πŸ’€

Condition code 2 on NQAP also means the send is incomplete, because a segment boundary was reached. The NQAP is repeated. so yeah, that’s the whole situation 🌸


🌈 SEE ALSO 🌈

Kernel file ./drivers/s390/crypto/ap_queue.c β€” that’s the kernel file, and here’s the whole friend group:


that’s the page, bestie πŸ’œ signing off with source/version ./drivers/s390/crypto, dated October 2026, and page __ap_send(9). bye and slay πŸ¦‹βœ¨

πŸ“¦ where this page comes from