fh_partition_start(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« fh_partition_start(9) πŸ’«

okay so bestie, welcome to the Kernel API Manual page for fh_partition_start β€” yes it's a real section 9 man page, yes it's from the kernel, and yes we're gonna get through it together 🫢


✨ NAME ✨

fh_partition_start β€” boots and starts execution of the specified partition πŸ”₯

Like, it's the "go go go" button for a partition. main character energy fr.


🌸 SYNOPSIS 🌸

unsigned int fh_partition_start (unsigned int partition , uint32_t
entry_point , int load );

ngl the line break in the middle of the parameter list is iconic of kernel headers, we love a spread-out signature πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • partition β€” the partition ID, i.e. which partition you're hyping up πŸ’–
  • entry_point β€” the guest physical address to start execution at. that's where the party begins ⭐
  • load β€” -- undescribed -- πŸ™ˆ okay so the man page literally does not describe this one. no cap, that's all it says. we are not making anything up about it, we're just observing that the docs left it blank πŸ’€

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: the hypervisor creates a 1-to-1 virtual/physical IMA mapping, which means at boot time, guest physical addresses are the same as guest virtual addresses. same address, both worlds, no translation drama ✨ lowkey elegant.

It returns 0 for success, or an error code. that's the whole contract. slay πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

Everything lives in the kernel file ./arch/powerpc/include/asm/fsl_hcalls.h β€” go read the whole friend group πŸ’œ


πŸ“ reminder bestie: load is literally labeled -- undescribed -- in the source. don't let anyone tell you otherwise, and don't go guessing what it does. we stay honest in this group chat 🫢

okay that's the whole page, and it's giving obscure-but-useful. sign-off time: this one comes from ./arch/powerpc/include/asm, dated October 2026 β€” so mark your calendar, she's a future icon πŸŒˆβœ¨πŸ’–

πŸ“¦ where this page comes from