STRUCT CALL_RETURN_PROCESSOR(9)

💅 struct call_return_processor — Kernel API Manual energy ✨

okay so bestie, welcome to the Kernel API Manual — this little page is all about struct call_return_processor, and no cap, the whole job of this thing is literally just: provide a call-back to consume call-return information. That's it. That's the vibe. It's a struct whose entire main-character arc is handing your callback some call-return tea so you can sip it. 🎀

✨ NAME ✨

struct call_return_processor — provides a call-back to consume call-return information. fr fr, that's the whole pitch. 🫶

🦋 SYNOPSIS 🦋

struct call_return_processor {
    struct call_path_root *cpr;
    int (*process)(struct call_return *cr, u64 *parent_db_id, void *data);
    void *data;
};

look at her. iconic. three members, zero drama (mostly). 💅

🌸 Members 🌸

• cpr — the call path root. it's the root of the call path situation, standing there being all root-y. 🌈
• process — the call-back that accepts call/return information. this is the main event, the callback, the one who actually gets handed the tea. 👑
• data — anonymous data for call-back. it's just vibes and a pointer, passed along for your callback to do whatever it wants with. no questions asked. 🙈

⭐ SEE ALSO ⭐

• Kernel file ./tools/perf/util/thread-stack.h
• struct call_return(9) — go read this one next bestie, they're literally linked 💜

okay that's the whole page, you ate that. stay hydrated, go read your call-return info responsibly 🍓

sign-off time: this lil beauty lives down in ./tools/perf/util, and the version of record is dated October 2026 — the header up top reads struct call_...rn_processor(9) (yes the truncation is canon, don't come for her) and the footer calls her struct call_...rn_processor(9) too. periodt. 🧚✨💖