emit_log_message(9)

💖 NAME 💖

okay so this is emit_log_message(9) from the Kernel API Manual, and it's literally the main-character page for emit_log_message — it emits a log message to the kernel log in a format suited to the current thread context. no cap, that's the whole vibe. 🫶

✨ SYNOPSIS ✨

here's the signature, character for character, bestie:

void emit_log_message (int priority , const char *module , const char *prefix , const struct va_format *vaf1 , const struct va_format *vaf2 );

🌸 ARGUMENTS 🌸

• priority — the priority at which to log the message. yes, the whole importance level, periodt.
• module — The name of the module doing the logging.
• prefix — The prefix of the log message.
• vaf1 — The first message format descriptor.
• vaf2 — The second message format descriptor.

🦋 DESCRIPTION 🦋

Context info formats, served fresh and honestly a little chaotic:

interrupt:           uds[NMI]: blah kvdo thread:         kvdo12:foobarQ:
blah thread w/device id:  kvdo12:myprog: blah other thread:        uds:
myprog: blah

Fields: module name, interrupt level, process name, device ID. iykyk 💅

🌈 SEE ALSO 🌈

Kernel file ./drivers/md/dm-vdo/logger.c, plus emit_log_message_to_kernel(9) — go click, bestie. ✨

mwah 💖 this little page comes from ./drivers/md/dm-vdo, dated October 2026 — emit_log_message(9) out. 🎀