eeh_pe_tree_insert(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– eeh_pe_tree_insert(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so this is a page from the Kernel API Manual (eeh_pe_tree_insert(9), yes the whole name is a mouthful, iykyk) and we're about to make it make sense. Strap in. πŸ¦‹


✨ NAME ✨

eeh_pe_tree_insert β€” literally just adds an EEH device to its parent PE. that's the whole vibe. πŸ’…


🌸 SYNOPSIS 🌸

int eeh_pe_tree_insert (struct eeh_dev *edev, struct eeh_pe *new_pe_parent);

like look at her. two params. does exactly what it says. main character energy fr. ⭐


πŸ’œ ARGUMENTS πŸ’œ

  • edev β€” the EEH device in question, the little guy we're placing πŸ‘‘
  • new_pe_parent β€” the PE you want to create extra PEs under, i.e. the parent-to-be 🫢

🌈 DESCRIPTION 🌈

so here's the tea β˜•: this function adds your EEH device to the PE sitting at edev->pe_config_addr.

if a PE already exists at that address? slay, no new object needed β€” edev just gets added to that existing PE. easy. ✨

but if there's no PE at that address yet? not me spawning a whole new PE 😭 β€” one gets created and inserted into the PE tree as a child of new_pe_parent. that's the whole plot.

and ooh, important detail bestie πŸ’€: if new_pe_parent is NULL, the new PE gets inserted directly under the PHB. no middleman, no cap.

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, gathered here for you 🫢 β€” and they all live in the kernel file ./arch/powerpc/kernel/eeh_pe.c:


mwah πŸ’‹ that's the page! brought to you from ./arch/powerpc/kernel, stamped October 2026, and it's eeh_pe_tree_insert(9) all the way down. go read the source, bestie, you got this πŸ’–βœ¨

πŸ“¦ where this page comes from