hvc_iucv_send(9)

💖 hvc_iucv_send(9) 💖

okay bestie, welcome to your Kernel API Manual moment ✨ this page is literally all about hvc_iucv_send, and it’s giving very specific terminal-data vibes. no cap.

🌸 NAME 🌸

hvc_iucv_send — Send an IUCV message containing terminal data.

✨ SYNOPSIS ✨

int hvc_iucv_send (struct hvc_iucv_private *priv );

🎀 ARGUMENTS 🎀

• priv — Pointer to a struct hvc_iucv_private instance. that’s the whole argument list, and she ate.

🦋 DESCRIPTION 🦋

So here’s the vibe 💅 if an IUCV communication path has been established, the buffered output data gets sent via an IUCV message, and the number of bytes sent is returned. slay, bytes delivered.

If there is no established IUCV communication path, it returns 0. if an existing IUCV communication path has been severed, it returns -EPIPE. severed path? tragic. -EPIPE says it all. 😭

💅 SEE ALSO 💅

Kernel file: ./drivers/tty/hvc/hvc_iucv.c

• hvc_iucv_get_private(9)
• alloc_tty_buffer(9)
• destroy_tty_buffer(9)
• destroy_tty_buffer_list(9)
• hvc_iucv_write(9)
• hvc_iucv_get_chars(9)
• hvc_iucv_queue(9)
• hvc_iucv_sndbuf_work(9)
• hvc_iucv_put_chars(9)
• hvc_iucv_notifier_add(9)
• hvc_iucv_cleanup(9)
• tty_outqueue_empty(9)
• flush_sndbuf_sync(9)
• hvc_iucv_hangup(9)
• hvc_iucv_notifier_hangup(9)
• hvc_iucv_dtr_rts(9)
• hvc_iucv_notifier_del(9)
• hvc_iucv_filter_connreq(9)
• hvc_iucv_path_pending(9)
• hvc_iucv_path_severed(9)
• hvc_iucv_msg_pending(9)
• hvc_iucv_msg_complete(9)
• hvc_iucv_alloc(9)
• hvc_iucv_destroy(9)
• hvc_iucv_parse_filter(9)
• hvc_iucv_setup_filter(9)
• param_set_vmidfilter(9)
• param_get_vmidfilter(9)
• hvc_iucv_init(9)
• hvc_iucv_config(9)

with love from the kernel-side group chat 🫶 source situation: ./drivers/tty/hvc, dated October 2026, page hvc_iucv_send(9) — bye bestie, stay buffered 💖✨