synth_event_add_fields(9)

📦 version 7.3.1, in nixpkgs unstable

✨ synth_event_add_fields(9) ✨

okay so bestie, we're in the Kernel API Manual today and this page is literally all about synth_event_add_fields — the glow-up move where you add a whole set of fields to a synthetic event cmd in one go instead of one at a time. iconique behavior, honestly 🫶

🌸 NAME 🌸

synth_event_add_fields — add multiple fields to a synthetic event cmd ✨ (yes, multiple, we love an efficient queen 💅)

🦋 SYNOPSIS 🦋

int synth_event_add_fields (struct dynevent_cmd *cmd , struct
synth_field_desc *fields , unsigned int n_fields );

🎀 ARGUMENTS 🎀

  • cmd — a pointer to the dynevent_cmd struct that's representing your brand-new event. main character struct energy 👑
  • fields — an array of type/name field descriptions. it's giving "here's the whole squad" 🧚
  • n_fields — the number of field descriptions chillin' in the fields array. count 'em, bestie 🔢

💖 DESCRIPTION 💖

So what this does: it adds a new set of fields to a synthetic event cmd object. lowkey the whole point. 🙈

The event fields that will be defined for your event should be passed in as an array of struct synth_field_desc, and the number of elements in that array gets passed in as n_fields. no cap, that's the whole vibe.

Field ordering will retain the ordering given in the fields array. so like, the order you give it is the order you get. respect the queue, periodt 💅

Also: go check out synth_field_size for the available types — that's where the type lore lives 👀. And if field_name contains [n], the field is considered to be an array. noted. ⭐

🔥 RETURN 🔥

0 if successful, error otherwise. that's it, that's the returns section fr fr 💀

🌈 SEE ALSO 🌈

Kernel file ./kernel/trace/trace_events_synth.c — the sacred text 📜

Then all these besties:

ngl the whole family is here, it's a whole reunion 🎉

okay that's the page!! it lives under ./kernel/trace 🍓 and it's dated October 2026 — so go forth and add those fields, bestie, you're gonna slay 💜✨

📦 where this page comes from