[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B5F518.3000708@windriver.com>
Date: Fri, 15 Feb 2008 14:24:56 -0600
From: Jason Wessel <jason.wessel@...driver.com>
To: Andi Kleen <andi@...stfloor.org>
CC: Jan Kiszka <jan.kiszka@...mens.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
"Frank Ch. Eigler" <fche@...hat.com>,
Roland McGrath <roland@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jan Kiszka <jan.kiszka@....de>
Subject: Re: [RFC][PATCH] modular kgdb-light
Andi Kleen wrote:
> On Fri, Feb 15, 2008 at 01:35:36PM +0100, Jan Kiszka wrote:
>
>> o machine_emergency_restart - for implementing "R0" gdb packet
>>
>
> Hmm, might be a bit dangerous to call this directly -- there are various
> quirks with e.g. not rebooting on CPU #0 and not resetting APIC
> state. But ok [this is not directly related to the fact that it's
> exported now, just mentioning this in general]
>
>
kgdb was never expected to be any better than using a sysrq-b. Unless
you put some really ugly code in to deal with lots of edge cases there
are certainly times it is just going to force you to press the power
button. If there is a better function for "reset now and cross fingers"
kgdb can be changed easily enough to do that.
Also given that you can have more than one type of "R" packet it would
be easy enough to add other reboot types, such as an R1 which might call
to the bios or another means to reset. For now the intent is pretty
clear and there is not likely a need to expand the scope.
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists