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