On Tue, Oct 23, 2012 at 07:17:33AM -0700, Kevin Hilman wrote:
Russell King - ARM Linux [off-list ref] writes:
quoted
No, printk() does not need this. You think it does, but it doesn't. What
we have is a difference between ARM and x86, and this difference is breaking
the scheduler.
The fact that the printk timestamp increments while suspended is a bug. It
doesn't on x86.
Russell, I agree that it's a bug, but does it qualify as a something
you're willing to take for v3.7-rc?
Definitely. Our current behaviour across suspend for the scheduler is
wrong. This is one of the questions I had when I created the sched_clock
stuff - but no one at the time could answer. So, now that we have our
answer, let's get it fixed to conform.