Re: report for the week of June 14 2009

From: Thomas Gleixner
Date: Tue Jun 23 2009 - 13:01:12 EST

On Tue, 23 Jun 2009, Rafael J. Wysocki wrote:
> The long term solution for the issue at hand is to clean up the suspend-resume
> support in cpufreq so that it doesn't do stupid things like calling
> smp_call_function_single() with interrupts disabled, but that requires someone
> (I can do it, but I need to dig through the cpufreq code for this purpose) to
> figure out how to fix it.
> I'm not quite sure if there's an acceptable short term solution, though.
> In principle we can do
> local_irq_save()
> ...
> local_irq_restore()
> around each sysdevs ->susend() and ->resume() in addition to checking the
> status of interrupts. Would that work?

Well not really, if the function enables interrupts you run into the
same issue (interrupt service routine calls ktime_get()) again.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at