has_valid_asid(9)

💅 has_valid_asid(9) 💅

welcome to the Kernel API Manual, bestie — today’s main character is has_valid_asid, and she’s here to answer one very specific question 🫶✨

---

🌸 NAME 🌸

has_valid_asid — Determine if an mm already has an ASID. 💖

---

✨ SYNOPSIS ✨

int has_valid_asid (const struct mm_struct *mm , unsigned int type );

---

🎀 ARGUMENTS 🎀

• mm — Memory map. 🗺️
• type — R4K_HIT or R4K_INDEX, type of cache op. 🔥

---

🦋 DESCRIPTION 🦋

okay so literally, this function determines whether mm already has an ASID on any of the CPUs which cache ops of type type within an r4k_on_each_cpu call will affect. 👀💅

If r4k_on_each_cpu does an SMP call to a single VPE in each core, then the scope of the operation is confined to sibling CPUs; otherwise, all online CPUs will need to be checked. 🧚✨

⚠️ vibe check: it must be called in non-preemptive context. no cap. 😭

---

🌈 RETURN 🌈

Returns 1 if the CPUs affected by type cache ops have an ASID for mm. 0 otherwise. ⭐

---

💜 SEE ALSO 💜

• Kernel file ./arch/mips/mm/c-r4k.c — also peep r4k_op_needs_ipi(9). 👑

---

mwah 💋 this page lives under ./arch/mips/mm, dated October 2026, and the footer literally says has_valid_asid(9) — bye bestie 🫶🎀