eeh_remove_event(9)

💅 eeh_remove_event(9) — like, the one from the Kernel API Manual, bestie

Okay so picture this: you're deep in the kernel, you've got an EEH event queue, and some of those events are literally just reruns of an event you already handled. Not me writing a whole manpage about deleting duplicates 😭 but here we are. Slay.

---

✨ NAME ✨

eeh_remove_event — remove an EEH event from the queue. That's it, that's the whole vibe. Gone. Deleted. Blocked. 💅

---

🦋 SYNOPSIS 🦋

void eeh_remove_event (struct eeh_pe *pe , bool force );

Look at her. Iconic signature. Note the exact spacing, we don't "fix" things here, that's her character 🎀

---

🌸 DESCRIPTION 🌸

So on the PowerNV platform, there's this whole situation: the events that come in after can turn out to be part of the former one. Like... they're not their own thing, they're just the same event showing up again in a different outfit 🙈

When that happens, those subsequent coming events are totally duplicated and unnecessary, and therefore they should be removed. Yeah. Off the queue. No notes.

That's the whole story — eeh_remove_event is the function that does the removing. Main character energy, honestly 👑

---

🎀 ARGUMENTS 🎀

• pe — the event binding to the PE. Yeah, it's a struct eeh_pe *, she's got opinions and a type. Fr fr.
• force — a bool, and when this is set the event will be removed unconditionally. No questions, no vibe check, it's just gone 💀

---

🧚 SEE ALSO 🧚

• Kernel file ./arch/powerpc/kernel/eeh_event.c
• eeh_event_handler(9)
• eeh_event_init(9)

Go read those too, they're the supporting cast and they ate 🔥

---

Lowkey a reminder: this page is documenting kernel API behaviour, so take the duplication thing seriously even while I'm out here being cute about it 🫶

---

⭐ okay bye babes, this page lives in ./arch/powerpc/kernel, it's dated October 2026, and that's the whole manual, periodt 💖