[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] cpuidle causing Dom0 soft lockups
>>> "Tian, Kevin" <kevin.tian@xxxxxxxxx> 05.02.10 12:16 >>> >Possible options is to take jiffies, system timestamp, and per-cpu >timestamp in stop_hz_timer, to generate a local latest value. Or >a per-cpu jiffies can be generated in per-cpu timer interrupt, which >is only used in per-cpu style like in stop_hz_timer. That was my next thought too - but it doesn't work (unless I made a blatant mistake). Not only does it not get the interrupt rate down, it even grows it on the duty CPU, and it creates visible brief hangs as well a rushes of time. Next I'll do is try to detect when the duty CPU is de-scheduled, and move on the duty to one that is scheduled (i.e. one that is currently executing timer_interrupt()). Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |