trace_ksm_start_scan(9)

📦 version 7.3.1, in nixpkgs unstable

💅 trace_ksm_start_scan(9) 💅

ok so bestie, welcome to the Kernel API Manual ✨ — this one's a lil tracepoint page, and honestly? it's giving "short but iconic." let's get into it 🎀

🌸 NAME 🌸

trace_ksm_start_scan — literally the function that gets called right after a brand-new ksm scan kicks off 🏁

✨ SYNOPSIS ✨

void trace_ksm_start_scan (int seq , u32 rmap_entries );

no cap, that's the whole signature — void, so it gives you nothing back, it's purely here to vibe and emit a trace 💫

🦋 ARGUMENTS 🦋

  • seq — the sequence number of the scan 🔢 iykyk, it's how you tell this scan apart from all the other scans
  • rmap_entries — the actual number of rmap entries 📊 (a u32, bestie, so plan accordingly)

🧚 DESCRIPTION 🧚

ok so real talk: this bad boy allows you to trace the start of a ksm scan 👑 that's the whole job. it shows up, it marks the beginning, it slays, it leaves. main character energy fr fr 💅

⭐ SEE ALSO ⭐

go look at the kernel file ./include/trace/events/ksm.h and then run through the whole friend group 🫶:

like, the whole ksm tracepoint squad is there — go say hi 🌈

💀 friendly reminder: everything above is exactly what the page says, no extra lore, no invented behaviour. i'm cute, not a source of new syscall facts 🙈

and that's the page, bestie!! 🍓 this lil gem lives in ./include/trace/events, dated October 2026 (yes, the future, we're time-traveling ✨), and it's literally titled trace_ksm_start_scan(9). mwah, go trace something gorgeous 💖🎀🦋

📦 where this page comes from