chsc_async(9)

✨ chsc_async ✨

okay so bestie, welcome to chsc_async(9) from the Kernel API Manual — this is the one that tries to start a chsc request asynchronously, and honestly? it's giving "I'll get to it when I get to it" energy and I respect it 💅

---

🎀 SYNOPSIS 🎀

int chsc_async (struct chsc_async_area *chsc_area , struct chsc_request
*request );

like, that's the whole signature, no cap — two pointers in, an int out 🫶

---

🌸 ARGUMENTS 🌸

• chsc_area — the request you want to be started, fr fr. that's the one that's gonna get launched ✨
• request — the request structure you want to associate with it 🦋

---

💖 DESCRIPTION 💖

So here's the vibe: this little icon tries to start a chsc request on one of the existing chsc subchannels. that's it, that's the whole main character moment 👑

ngl the word "tries" is doing a lot of heavy lifting there — check the return values before you get too comfortable 💀

---

⭐ RETURN ⭐

• 0 — the request was performed synchronously 🎀 (yes bestie, "async" function, synchronous result — I don't make the rules)
• -EINPROGRESS — the request was successfully started, slay 🔥
• -EBUSY — literally every chsc subchannel is busy rn, they're all booked 😭
• -ENODEV — no chsc subchannels are available at all, it's giving empty group chat 🙈

---

🦋 CONTEXT 🦋

this is the important bit, don't skip it:

• interrupts disabled
• chsc_lock held

periodt. if you're not in that exact context, that's a you problem 💅

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/s390/cio/chsc_sch.c — go read the source, iykyk 📖✨

---

and that's the page, bestie! 🫶 this little gem lives in ./drivers/s390/cio, and it's dated October 2026 — so yes, it's from the future, we stan a timeless classic 👑💜 mwah, go start some requests asynchronously (or don't, -EBUSY happens) 🎀🌸