Prev: [PATCH 4/5] x86: Merge kernel_math_error() into math_error()
Next: [PATCH 0/5] x86: Merge fpu and simd exception handlers
From: Arjan van de Ven on 18 Mar 2010 14:30
On 3/18/2010 10:49, Aaro Koskinen wrote:
> The clock used for printk.time=1 does not necessarily start running
> from zero. On such platforms the bootgraph does not work properly as
> the calculated boottime will be too long.

can we fix the platform to be smarter instead ? I'd think that's needed anyway for various
timers etc to actually work well

>
> To correct this, the patch modifies the script to accept only non-zero
> start times. This ensures the report contains entries only from the
> period when the clock was running.
>
> Signed-off-by: Aaro Koskinen<aaro.koskinen(a)nokia.com>

nothing wrong with the patch itself... just sad that it's needed to work around such bugs ;(

Acked-by: Arjan van de Ven <arjan(a)linux.intel.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 4/5] x86: Merge kernel_math_error() into math_error()
Next: [PATCH 0/5] x86: Merge fpu and simd exception handlers