Re: [PATCH] [RFC] Potential fix for leapsecond caused futex relatedload spikes
From: John Stultz
Date: Sun Jul 01 2012 - 13:29:31 EST
On 07/01/2012 09:56 AM, Prarit Bhargava wrote:
John, the issue is that clock_was_set calls on_each_cpu() -- which cannot be
called from interrupt context as it calls smp_call_function_many().
I don't think you can call call_was_set() from update_wall_time() as
update_wall_time() is called in interrupt context.
Thanks for pointing this out. Ben Blum also mentioned this last night,
but I missed the atomic bit instead of the xtime_lock issue.
Reworking the patch now.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/