4ded365124
In read-only mode (detected VM/QEMU/KVM) apply_pstate is a no-op so c.current_idx never advances. The previous log line was emitted whenever the *requested* target (n) differed from current_idx, regardless of whether the write actually fired — on QEMU that produced thousands of P0->P1 lines per boot even though no transition ever took place. Gate the info!() on whether current_idx actually changed. Also skip the dwell accumulation entirely on read-only hosts: writes cannot take effect, so the hysteresis counter is meaningless. The governor still tracks the target so the load value reflects real demand, but no work fires per poll. Closes Phase H of the LG Gram 16 (2025) S/P-state work.