Re: [PATCH] nvme: log when APST skips a state due to latency cap

[Keith Busch]

On Sat, May 23, 2026 at 07:45:52AM -0400, Mike Bommarito wrote:
> Add a dev_info_once() at the skip site that names the state, prints
> the actual exit_lat versus the current cap, and points the user at
> the module parameter to raise it.  Using _once keeps the line to a
> single instance per controller; users that want to see every probe
> event can still enable dev_dbg.

The "_once" is not actually once for each controller; it's just once.
Some people have found other similar debug prints to be confusing when
they have multiple controllers since it looks like the seemingly
problematic controller is not consistent across reboots.