From: Andi Kleen <andi@xxxxxxxxxxxxxx> Date: Wed, 24 Jun 2009 09:53:42 +0200 >> > Ah you have a one shot timer and it gets rescheduled in the softirq? >> > If yes why not in doing that directly in the hardirq handler? >> >> Then what's the point of the generic timer code supporting one-shot >> clock sources? :-) > > Well it would avoid that problem at least (I think based on your > description). Somehow you need to reschedule the timer before the softirq. > > I guess you could have a generic function that is callable from hardirq > directly? I'll think a bit more about this, thanks Andi. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
