trace_purge_vmap_area_lazy(9)

💖 trace_purge_vmap_area_lazy 💖

Okay so welcome to the Kernel API Manual, bestie! This page is all about trace_purge_vmap_area_lazy(9) — the tracepoint that fires when vmap areas get lazily freed. It's giving "cleanup era" energy 🧹✨

✨ NAME ✨

trace_purge_vmap_area_lazy — called when vmap areas were lazily freed. Periodt. 💅

🌸 SYNOPSIS 🌸

void trace_purge_vmap_area_lazy (unsigned long start , unsigned long end
, unsigned int npurged );

🎀 ARGUMENTS 🎀

• start — the purging start address, aka where the purge zone begins 🗺️
• end — the purging end address, aka where the purge zone ends 🏁
• npurged — numbed of purged vmap areas (yes, "numbed" is literally what it says, no cap 😭). Basically the count of how many vmap areas got purged.

💜 DESCRIPTION 💜

So this event is literally just for a debug purpose, bestie. It's not out here doing main character energy in production — it's a debug vibe check. It gives you some indication about the start:end range and how many objects are released. That's it, that's the tweet. 🐦

Ngl, it's basically a "hey bestie, here's the cleanup report" situation. Useful for debugging, not for your everyday kernel drama. 💀

🌈 SEE ALSO 🌈

• Kernel file ./include/trace/events/vmalloc.h
• trace_alloc_vmap_area(9)
• trace_free_vmap_area_noflush(9)

And that's the whole page, bestie! 🫶 This gem came from ./include/trace/events, dated October 2026, and it's the manual for trace_purge_vmap_area_lazy(9). Byeee, ily! 💖✨