synth_event_add_field(9)

💅 synth_event_add_field(9) 💅

okay so this is a page from the Kernel API Manual, and bestie, we're about to add a field to a synthetic event cmd. slay. let's get into it 🫶

---

✨ NAME ✨

synth_event_add_field — adds a shiny new field to a synthetic event cmd 🌸

✨ SYNOPSIS ✨

int synth_event_add_field (struct dynevent_cmd *cmd , const char *type ,
       const char *name );

✨ ARGUMENTS ✨

• cmd — a pointer to the dynevent_cmd struct that's representing the new event. like, this is the whole vibe container 💜
• type — the type of the new field you're adding. yep, that's the one.
• name — the name of the new field you're adding. iconic of it.

✨ DESCRIPTION ✨

so basically you're adding a new field to a synthetic event cmd object. and here's the cute part: field ordering is in the same order the fields are added. so like, first in, first listed. no cap, order matters 🎀

also, go check out synth_field_size for the available types — that's where the type menu lives, iykyk. and heads up: if field_name contains [n], the field is considered to be an array. literally that's it, that's the rule ✨

✨ RETURN ✨

0 if successful, error otherwise. that's the whole thing. zero means we ate, anything else means something's off 😭

✨ SEE ALSO ✨

• Kernel file ./kernel/trace/trace_events_synth.c
• synth_event_add_field_str(9)
• synth_event_add_fields(9)
• __synth_event_gen_cmd_start(9)
• synth_event_gen_cmd_array_start(9)
• synth_event_create(9)
• synth_event_delete(9)
• synth_event_cmd_init(9)
• synth_event_trace(9)
• synth_event_trace_array(9)
• synth_event_trace_start(9)
• synth_event_add_next_val(9)
• synth_event_add_val(9)
• synth_event_trace_end(9)

---

bestie the whole friend group is in SEE ALSO. go read them. it's giving study group energy 📚💅

---

and that's the page!! this one lives over in ./kernel/trace and it's dated October 2026 — so like, future-era kernel lore ⭐ thanks for reading, mwah 💖🦋