Re: [PATCH] softlockup: fix problem with long kernel pauses fromkgdb

[Ingo Molnar <mingo@elte.hu>]

* Jason Wessel <jason.wessel@windriver.com> wrote:

> Ingo Molnar wrote:
> > * Jason Wessel <jason.wessel@windriver.com> wrote:
> > 
> >> -----
> >> From: Jason Wessel <jason.wessel@windriver.com>
> >> Subject: [PATCH] softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume
> >>
> >> When CONFIG_HAVE_UNSTABLE_SCHED_CLOCK is set sched_clock() gets the
> >> time from hardware, such as from TSC.  In this configuration kgdb will
> >> report a softlock warning messages on resuming or detaching from a
> >> debug session.
> >>
> > 
> > Hm, this looks quite ugly. Peter, Thomas, can you think of a 
> > cleaner solution?
> > 
> 
> Below was a more specific test case I received from Dongdong Deng 
> which did not require kgdb.  The test case is not something to 
> merge, it is just a simple module to build to demonstrate the 
> problem outside of kgdb.
> 
> The patch I submitted might have been on the "ugly" side, but 
> there was not an obvious way to solve the problem without making 
> changes in kernel/sched*.  I opted for something that was entirely 
> self contained to the softlockup code.

it's not really the fault of your patch really - all these 
integrations along dynticks, scheduler time and softlockup feel a 
bit awkward. Wondering whether there's some nicer way.

	Ingo