From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [Patch] IA64 Kexec/Kdump patch for 2.6.18-rc6
Date: Tue, 19 Sep 2006 22:39:10 +0000 [thread overview]
Message-ID: <27935.1158705550@ocs3.ocs.com.au> (raw)
In-Reply-To: <BAC6D88895D68Findou.takao@jp.fujitsu.com>
Gerald Pfeifer (on Tue, 19 Sep 2006 12:13:15 +0200 (CEST)) wrote:
>On Fri, 15 Sep 2006, Keith Owens wrote:
>> I am back from vacation and am now working on a common 'crash stop'
>> synchronization interface that can be used by all the debug[*] tools,
>> instead of everybody inventing their own and tripping over each other.
>> Obviously it is based on the KDB patch, but it will be generic enough
>> that anybody can use it.
>>
>> [*] Using the term 'debug' generically here. It can be a debugger like
>> kdb, kgdb, nlkd or a crash dump tool like lkcd, crash or kexec.
>> They all have the same synchronization requirements, stop all cpus
>> using NMI/INIT where necessary and save the state of all the cpus
>> for later diagnosis.
>
>Will this allow to have LKCD and kexec/kdump enabled in the same kernel,
>selectable by the user at boot time (via a kernel command-line option,
>for example)?
The 'crash stop' code can be used by any tool to use but does not
impose any policy on the user. The choice of which debug tool to use
is left to the user.
next prev parent reply other threads:[~2006-09-19 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 5:34 [Fastboot] [Patch] IA64 Kexec/Kdump patch for 2.6.18-rc6 Takao Indoh
2006-09-15 5:58 ` Takao Indoh
2006-09-15 7:27 ` Keith Owens
2006-09-15 14:09 ` Don Zickus
2006-09-19 10:13 ` Gerald Pfeifer
2006-09-19 22:39 ` Keith Owens [this message]
2006-09-22 4:09 ` [Fastboot] [Patch] ia64 Kexec/Kdump patch for 2.6.18 Horms
2006-09-22 7:39 ` Horms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27935.1158705550@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox