Messages in this thread | | | Subject | Re: [patch 03/23] GTOD: persistent clock support, i386 | From | Thomas Gleixner <> | Date | Wed, 04 Oct 2006 01:30:00 +0200 |
| |
On Mon, 2006-10-02 at 15:44 -0700, Andrew Morton wrote: > > - write_seqlock_irqsave(&xtime_lock, flags); > > - jiffies_64 += sleep_length; > > - write_sequnlock_irqrestore(&xtime_lock, flags); > > touch_softlockup_watchdog(); > > return 0; > > } > > In this version of the patch, you no longer remove the > touch_softlockup_watchdog() call from timer_resume(). > > But clockevents-drivers-for-i386.patch deletes timer_resume() > altogether. > > Hence we might need to put that re-added touch_softlockup_watchdog() call > into somewhere else now.
clockevents has is it in the resume path.
static void clockevents_resume_local_events(void *arg) { .... touch_softlockup_watchdog(); }
tglx
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |