On Fri, 21 Sep 2012, Paul E. McKenney wrote:
> Good catch! Even worse, it gives "timer=18446744073709551615" on
> 64-bit systems, which is no easier on the eyes. I therefore changed
> the code to print a nicer message in this case, patch below.
Looks better, thanks.
- Paul
--
To unsubscribe
On Fri, Sep 21, 2012 at 04:13:29PM +, Paul Walmsley wrote:
>
> The CONFIG_RCU_FAST_NO_HZ stall warning messages can never emit
> "timer=-1". This is because the printf() format specifier to generate
> that number is '%lu'. So, update the documentation to use the
> unsigned long equivalent
The CONFIG_RCU_FAST_NO_HZ stall warning messages can never emit
"timer=-1". This is because the printf() format specifier to generate
that number is '%lu'. So, update the documentation to use the
unsigned long equivalent instead, "timer=4294967295". This is what
actually shows up in traces.
The CONFIG_RCU_FAST_NO_HZ stall warning messages can never emit
timer=-1. This is because the printf() format specifier to generate
that number is '%lu'. So, update the documentation to use the
unsigned long equivalent instead, timer=4294967295. This is what
actually shows up in traces.
On Fri, Sep 21, 2012 at 04:13:29PM +, Paul Walmsley wrote:
The CONFIG_RCU_FAST_NO_HZ stall warning messages can never emit
timer=-1. This is because the printf() format specifier to generate
that number is '%lu'. So, update the documentation to use the
unsigned long equivalent instead,
On Fri, 21 Sep 2012, Paul E. McKenney wrote:
Good catch! Even worse, it gives timer=18446744073709551615 on
64-bit systems, which is no easier on the eyes. I therefore changed
the code to print a nicer message in this case, patch below.
Looks better, thanks.
- Paul
--
To unsubscribe from
6 matches
Mail list logo