ps3_enable_pm(9)
π NAME π
ps3_enable_pm β bestie, this is the one that turns on the entire performance monitoring unit. Like, the whole thing. All of it. Periodt. π
β¨ SYNOPSIS β¨
void ps3_enable_pm (u32 cpu );
That's it. That's the whole call. Short and iconic. π
π«Ά ARGUMENTS π«Ά
cpuβ okay so, tragic lore: the docs literally just say-- undescribed --. No cap, that's the entire description in the source. So we're not gonna sit here and invent lore for it β it's au32 cpuand the manpage is staying mysterious about it. iykyk π
πΈ DESCRIPTION πΈ
Okay so here's the vibe: when we enable the LPM, all pending writes to counters get committed. That's the whole tea. π
Like β the moment the LPM gets switched on, anything that was still floating around waiting to hit the counters? It lands. Committed. Done. Slay. β¨
π₯ SEE ALSO π₯
So you're gonna wanna peek at the kernel file ./drivers/ps3/ps3-lpm.c for context (main character file, honestly), plus the whole friend group:
struct ps3_lpm_shadow_regs(9)struct ps3_lpm_priv(9)ps3_read_phys_ctr(9)ps3_write_phys_ctr(9)ps3_read_ctr(9)ps3_write_ctr(9)ps3_read_pm07_control(9)ps3_write_pm07_control(9)ps3_read_pm(9)ps3_write_pm(9)ps3_get_ctr_size(9)ps3_set_ctr_size(9)ps3_disable_pm(9)ps3_lpm_copy_tb(9)ps3_lpm_copy_tb_to_user(9)ps3_get_and_clear_pm_interrupts(9)ps3_enable_pm_interrupts(9)ps3_lpm_open(9)ps3_lpm_close(9)
Go read them all, bestie, they're all part of the same little ecosystem and honestly they ate. π
π§ little sign-off moment: this page lives at./drivers/ps3, dated October 2026, and it's serving youps3_enable_pm(9)β Kernel API Manual energy only. Bye bestie, go enable that PM unit, mwah ππβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms