| To: | jidong xiao <jidong.xiao@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 018/18] kdb-add-kdump-cmd |
| From: | Joe Korty <joe.korty@xxxxxxxx> |
| Date: | Fri, 11 Jul 2008 13:54:26 -0400 |
| Cc: | "kdb@xxxxxxxxxxx" <kdb@xxxxxxxxxxx>, "Houston, Jim" <jim.houston@xxxxxxxx> |
| In-reply-to: | <4104961b0807110824k512b492v17dff270dd832c2a@xxxxxxxxxxxxxx> |
| References: | <200807102053.m6AKrdRb031273@xxxxxxxxxxxxxx> <4104961b0807102316k7c62b1d3s47fd744b578d7280@xxxxxxxxxxxxxx> <20080711143747.GA9299@xxxxxxxxxxxxxxxx> <4104961b0807110824k512b492v17dff270dd832c2a@xxxxxxxxxxxxxx> |
| Reply-to: | Joe Korty <joe.korty@xxxxxxxx> |
| Sender: | kdb-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Fri, Jul 11, 2008 at 11:24:44AM -0400, jidong xiao wrote: > If I understand correctly, you are trying to add kexec/kdump > functionality into kdb. say, input "kdump" after the kdb prompt, then > kdump will begin to dump. > > This is actually already implemented by Dan some time back, you can > refer to following link, > http://www.mail-archive.com/kdb@xxxxxxxxxxx/msg01358.html Hi Jason, That patch doesn't seem to have made it into kdb, which is why I missed it. In fact I like the version I submitted better. It is smaller and is architecture-agnostic as well. But I don't mind if it is dropped. There is always the sysRQ method of invoking a crash dump to fall back on. Regards, Joe --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 20/20] kdb-clocksource-resync, joe . korty |
|---|---|
| Next by Date: | Re: [PATCH 000/18] Introduction, Jay Lan |
| Previous by Thread: | Re: [PATCH 018/18] kdb-add-kdump-cmd, jidong xiao |
| Next by Thread: | [PATCH 007/18] kdb-touch-nmi-watchdog, quilt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |