|| ||Thomas Gleixner <tglx-AT-linutronix.de> |
|| ||Dongdong Deng <libfetion-AT-gmail.com> |
|| ||Re: [PATCH 3/4] kgdb,clocksource: Prevent kernel hang in kernel debugger |
|| ||Tue, 26 Jan 2010 12:16:41 +0100 (CET)|
|| ||Martin Schwidefsky <schwidefsky-AT-de.ibm.com>,
Jason Wessel <jason.wessel-AT-windriver.com>,
mingo-AT-elte.hu, John Stultz <johnstul-AT-us.ibm.com>,
Andrew Morton <akpm-AT-linux-foundation.org>,
Magnus Damm <damm-AT-igel.co.jp>|
|| ||Article, Thread
On Tue, 26 Jan 2010, Thomas Gleixner wrote:
> There is no sane way to reliably prevent TSC from becoming unstable
> when kgdb stops the kernel inside the watchdog code. And I do not care
> about that at all.
> I'm not going to clutter code with crazy workarounds just because some
> people believe that using a kernel debugger is a good idea. If people
> insist on using kgdb then the possible "TSC becomes unstable" side
> effect is the least of their problems.
Btw, if the kernel uses tick based timekeeping or a clock source which
wraps in rather short intervals (e.g. pm-timer wraps after ~4.6
seconds), stopping the kernel with kgdb will inevitably screw up time
So there is really no reason to worry about TSC becoming unstable.
There is only one real sensible solution for this:
Do _not_ use kgdb - which is the modus operandi of every sane kernel
developer on the planet.
to post comments)