iucv_allow_cpu(9)

🌸 NAME 🌸

Okay so welcome to the Kernel API Manual, section 9 — manual name folded in near the top, slay. This page is all about iucv_allow_cpu, and its whole personality is literally “Allow iucv interrupts on this cpu.” That's the assignment, bestie. No cap. 💅

🎀 SYNOPSIS 🎀

void iucv_allow_cpu (void *data );

The way this signature is giving clean-and-simple main character energy: returns void, takes one void *data. Copy it exactly, spaces and all. ✨

💖 ARGUMENTS 💖

• data — unused. That's the entire note, fr fr. It's there, it's a parameter, and it does not do a thing. 🫶

🦋 SEE ALSO 🦋

First up, the Kernel file: ./net/iucv/iucv.c. Then the whole friend group of related calls — and yes, I'm listing every single one because we do not skip the crew:

• __iucv_call_b2f0(9)
• iucv_block_cpu(9)
• iucv_declare_cpu(9)
• iucv_retrieve_cpu(9)
• iucv_sever_pathid(9)
• __iucv_cleanup_queue(9)
• iucv_cleanup_queue(9)
• iucv_register(9)
• iucv_unregister(9)
• iucv_path_accept(9)
• iucv_path_connect(9)
• iucv_path_quiesce(9)
• iucv_path_resume(9)
• iucv_path_sever(9)
• iucv_message_purge(9)
• iucv_message_receive_iprmdata(9)
• __iucv_message_receive(9)
• iucv_message_receive(9)
• iucv_message_reject(9)
• iucv_message_reply(9)
• __iucv_message_send(9)
• iucv_message_send(9)
• iucv_message_send2way(9)
• iucv_path_pending(9)
• iucv_path_complete(9)
• iucv_path_severed(9)
• iucv_path_quiesced(9)
• iucv_path_resumed(9)
• iucv_message_complete(9)
• iucv_message_pending(9)
• iucv_init(9)
• iucv_exit(9)

Source/version ./net/iucv, dated October 2026 — that's the footer vibe, page iucv_allow_cpu(9), signing off. Stay iconic, bestie. 💜✨