fh_partition_memcpy(9)

💅 fh_partition_memcpy(9) — Kernel API Manual

okay bestie, welcome to the fh_partition_memcpy page, straight out of the Kernel API Manual ✨ literally the whole manual name is right there, we're not hiding it. this is the group chat where hypervisor calls get explained 💖

---

🌸 NAME 🌸

fh_partition_memcpy — copies data from one guest to another 🫶

like, actually moving bytes between guests. no cap.

---

✨ SYNOPSIS ✨

unsigned int fh_partition_memcpy (unsigned int source , unsigned int
target , phys_addr_t sg_list , unsigned int count );

she takes four args and gives you back an unsigned int, periodt.

---

🎀 ARGUMENTS 🎀

• source — the ID of the partition to copy from 💫 (the giver, the origin, the main character of this transfer)
• target — the ID of the partition to copy to 🎯 (the receiver, the one getting the data delivered)
• sg_list — guest physical address of an array of fh_sg_list structures 📋 (yes, phys_addr_t, write that down)
• count — the number of entries in sg_list 🔢 (how many structs are actually in that array, bestie)

---

🦋 DESCRIPTION 🦋

Returns 0 for success, or an error code. that's the whole vibe check honestly 😭 zero means slay, anything else means something went sideways and you get an error code back.

ngl the manpage is short here — but that's literally all it says, so I'm not gonna invent lore. 0 = success 🎉, error code = not success 💀.

---

👑 SEE ALSO 👑

Kernel file ./arch/powerpc/include/asm/fsl_hcalls.h

and the whole friend group 💜:

• fh_send_nmi(9)
• fh_partition_get_dtprop(9)
• fh_partition_restart(9)
• fh_partition_get_status(9)
• fh_partition_start(9)
• fh_partition_stop(9)
• struct fh_sg_list(9)
• fh_dma_enable(9)
• fh_dma_disable(9)
• fh_vmpic_get_msir(9)
• fh_system_reset(9)
• fh_err_get_info(9)
• fh_get_core_state(9)
• fh_enter_nap(9)
• fh_exit_nap(9)
• fh_claim_device(9)

---

🌈 okay that's the page!! sourced from ./arch/powerpc/include/asm, dated October 2026, and we ate that 💅 mwah 🫶✨