[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH] x86/NMI: refine "watchdog stuck" log message
On Wed, Jan 24, 2024 at 04:21:24PM +0100, Jan Beulich wrote: > Observing > > "Testing NMI watchdog on all CPUs: 0 stuck" > > it felt like it's not quite right, but I still read it as "no CPU stuck; > all good", when really the system suffered from what 6bdb965178bb > ("x86/intel: ensure Global Performance Counter Control is setup > correctly") works around. Convert this to > > "Testing NMI watchdog on all CPUs: {0} stuck" To make this even more obvious, maybe it could be prefixed with "error": "Testing NMI watchdog on all CPUs: error {0} stuck" Hm, albeit I don't like it that much > > or, with multiple CPUs having an issue, e.g. > > "Testing NMI watchdog on all CPUs: {0,40} stuck" > > to make more obvious that a lone number is not a count of CPUs. > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> > --- > In principle "sep" could also fulfill the job of "ok"; it felt to me as > if this may not be liked very much, though. I think I prefer it the current way. Thanks, Roger.
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |