Re: kgdb Bad IO access

[Jason Wessel <jason.wessel@windriver.com>]

Tilman Schmidt wrote:
> Apart from that, the kernel runs fine, though its subjectively a bit
> sluggish compared to 2.6.22-rc6-mm1 without kgdb. Its uname -a is:
> Linux xenon 2.6.22-rc6-mm1-test4 #10 SMP PREEMPT Thu Jul 5 23:41:32 CEST 2007 i686 i686 i386 GNU/Linux
> I didn't even try to actually do anything with kgdb, though.
>
>   

Do you have something that is more than subjective as a measure?  Some 
app runs slower, or it boots x seconds slower?

The only place I could foresee that kgdb could be eating extra cycles in 
the runtime case is from the die_notifier processing.  Any kind of 
exception such as a page fault, trap etc... will have a few extra ops 
and checks of variables so as to determine if the debugger should take 
the exception.  It looks to me like it would even benefit to add the 
check at the top of the notify hook for kgdb to exit immediately if the 
debugger is not attached.

I have contemplated making some changes to KGDB so as to make the 
registration to the die_notifier to be dynamic with attaching and 
detaching of the debugger.  If this is done, I would also make a change 
to allow for the case where the kernel would wait for the debugger to 
attach on any fatal fault.

Jason.



-
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/