On 27 February 2013 10:26, Santosh Shilimkar <[email protected]> wrote: > On Wednesday 27 February 2013 03:47 AM, Daniel Lezcano wrote: >> >> From: Viresh Kumar <[email protected]> >> >> When a cpu goes to a deep idle state where its local timer is shutdown, it >> notifies the time frame work to use the broadcast timer instead. >> >> Unfortunately, the broadcast device could wake up any CPU, including an >> idle one >> which is not concerned by the wake up at all. >> > Broad-cast device will only open the CPU for which the timer IRQ > affined to. And infact with subject series the affinity also is > updated for the CPU which owns the last timer expiry event. > > What am I missing here ?
Dynamic affinity will work only if the following flag is set for a clock_event_device: CLOCK_EVT_FEAT_DYNIRQ, otherwise wakeup would happen on the cpu to which static affinity was set to. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
