__eeh_pe_get(9)

📦 version 7.3.1, in nixpkgs unstable

💖 __eeh_pe_get (9) — the Kernel API Manual, bestie edition 💖

okay so we're in the Kernel API Manual, section 9, and today's main character is __eeh_pe_get 🎀 she's a tiny little helper and her whole job is literally just checking a PE address. that's it. that's the vibe check. ✨

🌸 NAME 🌸

__eeh_pe_get — Check the PE address 💅

🦋 SYNOPSIS 🦋

void * __eeh_pe_get (struct eeh_pe *pe , void *flag );

like, she takes two things and hands you back a void *. no cap. 🫶

🌈 ARGUMENTS 🌈

  • pe — ngl, the manpage literally just says -- undescribed -- 😭 so we're keeping it 100% honest here: undescribed. that's all we got.
  • flag — same situation bestie, -- undescribed -- 🙈 no further info given.
listen, i can't make stuff up, that would be lying to your face and we don't do that here 💀 the docs just left those two blank, iconic behaviour honestly 👑

⭐ DESCRIPTION ⭐

okay so picture one particular PE — one specific little guy. she can be identified in two ways:

  1. by her PE address, or
  2. by the traditional BDF address 🎀

and the BDF address is made up of the Bus/Device/Function number, which is giving very much "three besties in a trench coat" energy 🧚

so how does the function know which one you want? that's where flag comes in — the extra data referred to by flag indicates which type of address should be used. periodt. 💅

💜 SEE ALSO 💜

like, that's a whole friend group right there 🔥 go say hi to all of them, iykyk 🌸

💀 fr fr reminder: pe and flag are literally labelled -- undescribed -- in the source docs, so if you were hoping for deep lore on those two… there isn't any. we stay truthful 🫶

and that's the whole page bestie!! 🌟 this iconic little number comes to you from ./arch/powerpc/kernel, dated October 2026, and it's __eeh_pe_get(9) all day every day 👑💖 bye ily, go check those PE addresses 🦋✨

📦 where this page comes from