__flush_cache_one(9)

💖 NAME 💖

Okay so this is __flush_cache_one(9) from the Kernel API Manual, and we're diving in bestie.

• __flush_cache_one — that's the name, and the original page leaves the description blank. Not me being mysterious, it's literally just the name and a dash. No cap. 💅

---

✨ SYNOPSIS ✨

Here's the whole signature, and yes you should copy it exactly:

void __flush_cache_one (unsigned long addr , unsigned long phys ,
       unsigned long exec_offset );

---

🎀 ARGUMENTS 🎀

• addr — address in memory mapped cache array. That's the vibe: it's an address sitting in the memory mapped cache array. 🦋
• phys — P1 address to flush. And bestie, listen: it has to match tags if addr has the 'A' bit set, i.e. associative write. That's a real condition, not a suggestion. 🙈
• exec_offset — set to 0x20000000 if the flush has to be executed from the P2 region, else 0x0. Two options, icon behavior only. ✨

---

🦋 DESCRIPTION 🦋

The description on this page is giving "sentence that walked offstage mid-sentence," and I'm not gonna pretend otherwise. Here's the original line in all its unfinished glory:

The offset into the cache array implied by 'addr' selects the operation (purge/write-back) is selected by the lower 2 bits of

Yep. It literally ends on "of." That's the whole sentence, no extra words from me, because inventing the rest would be a choice and we don't do that here. 😭💀

---

🌸 SEE ALSO 🌸

• Kernel file ./arch/sh/mm/cache-sh4.c — that's the kernel file the page points you at. Go give it a look, iykyk. 🫶

---

That's the whole page, bestie 💜 — brought to you by ./arch/sh/mm, dated October 2026, and it's __flush_cache_one(9) forever and always. Slay. 💅✨