LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: vgoyal@in.ibm.com
Cc: Takenori Nagano <t-nagano@ah.jp.nec.com>,
k-miyoshi@cb.jp.nec.com, Bernhard Walle <bwalle@suse.de>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Keith Owens <kaos@ocs.com.au>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] add kdump_after_notifier
Date: Tue, 21 Aug 2007 06:18:31 -0700 [thread overview]
Message-ID: <46CAE627.7070908@sgi.com> (raw)
In-Reply-To: <20070817105630.GA18167@in.ibm.com>
Vivek Goyal wrote:
> On Thu, Aug 16, 2007 at 06:26:35PM +0900, Takenori Nagano wrote:
>> Vivek Goyal wrote:
>> > So for the time being I think we can put RAS tools on die notifier list
>>> and if it runs into issues we can always think of creating a separate list.
>>>
>>> Few things come to mind.
>>>
>>> - Why there is a separate panic_notifier_list? Can't it be merged with
>>> die_chain? die_val already got one of the event type as PANIC. If there
>>> are no specific reasons then we should merge the two lists. Registering
>>> RAS tools on a single list is easier.
>> I think it is difficult, because die_chain is defined by each architecture.
>>
>
> I think die_chain is arch independent definition (kernel/die_notifier.c)?
> But anyway, to begin with it can be done only for panic_notifier.
>
>>> - Modify Kdump to register on die_chain list.
>>> - Modify Kdb to register on die_chain list.
>>> - Export all the registered members of die_chain through sysfs along with
>>> their priorities. Priorities should be modifiable. Most likely one
>>> shall have to introduce additional field in struct notifier_block. This
>>> field will be a string as an identifier of the user registerd. e.g
>>> "Kdump", "Kdb" etc.
>>>
>>> Now user will be able to view all the die_chain users through sysfs and
>>> be able to modify the order in which these should run by modifying their
>>> priority. Hence all the RAS tools can co-exist.
>> This is my image of your proposal.
>>
>> - Print current order
>>
>> # cat /sys/class/misc/debug/panic_notifier_list
>> priority name
>> 1 IPMI
>> 2 watchdog
>> 3 Kdb
>> 4 Kdump
>>
>
> I think Bernhard's suggestion looks better here. I noticed that
> /sys/kernel/debug is already present. So how about following.
>
> /sys/kernel/debug/kdump/priority
> /sys/kernel/debug/kdb/priority
> /sys/kernel/debug/IPMI/priority
Why separate priority files is better than a central file?
At least i think you get a grand picture of priority being
defined for all parties with a central file?
What do we decide priority if more than one component has
the same priority value?
Thanks,
- jay
>
> I think at some point of time we shall have to create another file say
> description.
>
> /sys/kernel/debug/IPMI/description
>
> Which can tell what does this tool do? Other a user might not have any
> clue how to prioritize various things.
>
> Thanks
> Vivek
>
next prev parent reply other threads:[~2007-08-21 13:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 12:15 Takenori Nagano
2007-07-26 14:07 ` Bernhard Walle
2007-07-26 15:32 ` Vivek Goyal
2007-07-26 15:34 ` Bernhard Walle
2007-07-26 15:44 ` Vivek Goyal
2007-07-26 15:47 ` Bernhard Walle
2007-07-26 15:54 ` Vivek Goyal
2007-07-26 16:14 ` Bernhard Walle
2007-07-26 16:21 ` Bernhard Walle
2007-07-26 23:28 ` Takenori Nagano
2007-07-30 9:16 ` Vivek Goyal
2007-07-30 13:42 ` Eric W. Biederman
2007-07-31 5:55 ` Takenori Nagano
2007-07-31 6:53 ` Eric W. Biederman
2007-08-01 9:26 ` Takenori Nagano
2007-08-01 10:00 ` Eric W. Biederman
2007-08-02 8:11 ` Takenori Nagano
2007-08-02 11:28 ` Vivek Goyal
2007-08-03 4:05 ` Keith Owens
2007-08-03 6:25 ` Andrew Morton
2007-08-03 6:34 ` Keith Owens
2007-08-03 7:37 ` Andrew Morton
2007-08-03 7:10 ` Eric W. Biederman
2007-08-05 11:07 ` Vivek Goyal
2007-08-14 8:34 ` Takenori Nagano
2007-08-14 8:37 ` Bernhard Walle
2007-08-14 8:48 ` Takenori Nagano
2007-08-14 8:53 ` Bernhard Walle
2007-08-14 13:24 ` Vivek Goyal
2007-08-16 9:26 ` Takenori Nagano
2007-08-16 9:45 ` Bernhard Walle
2007-08-17 10:56 ` Vivek Goyal
2007-08-21 7:45 ` Takenori Nagano
2007-08-23 3:52 ` Vivek Goyal
2007-08-21 13:18 ` Jay Lan [this message]
2007-08-21 13:21 ` Bernhard Walle
2007-08-23 3:56 ` Vivek Goyal
2007-08-23 17:34 ` Jay Lan
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=46CAE627.7070908@sgi.com \
--to=jlan@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=ebiederm@xmission.com \
--cc=k-miyoshi@cb.jp.nec.com \
--cc=kaos@ocs.com.au \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-nagano@ah.jp.nec.com \
--cc=vgoyal@in.ibm.com \
--subject='Re: [patch] add kdump_after_notifier' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).