All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: vgoyal@in.ibm.com
Cc: 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 16:45:02 +0900	[thread overview]
Message-ID: <46CA97FE.90505@ah.jp.nec.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.

I think die_val (notify_die() argument) values are arch independent.
They are defined in include/asm-<arch>/kdebug.h.

Your idea is good, but I think it has very large impact. It is very hard to fix
them at the same time. So, how about putting off merging two lists?

 > 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

Good.

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

Good idea. :-)

Thanks

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: vgoyal@in.ibm.com
Cc: Keith Owens <kaos@ocs.com.au>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	k-miyoshi@cb.jp.nec.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Bernhard Walle <bwalle@suse.de>
Subject: Re: [patch] add kdump_after_notifier
Date: Tue, 21 Aug 2007 16:45:02 +0900	[thread overview]
Message-ID: <46CA97FE.90505@ah.jp.nec.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.

I think die_val (notify_die() argument) values are arch independent.
They are defined in include/asm-<arch>/kdebug.h.

Your idea is good, but I think it has very large impact. It is very hard to fix
them at the same time. So, how about putting off merging two lists?

 > 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

Good.

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

Good idea. :-)

Thanks

  reply	other threads:[~2007-08-21  7:45 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 12:15 [patch] add kdump_after_notifier Takenori Nagano
2007-07-19 12:15 ` Takenori Nagano
2007-07-26 14:07 ` Bernhard Walle
2007-07-26 14:07   ` Bernhard Walle
2007-07-26 15:32   ` Vivek Goyal
2007-07-26 15:32     ` Vivek Goyal
2007-07-26 15:34     ` Bernhard Walle
2007-07-26 15:34       ` Bernhard Walle
2007-07-26 15:44       ` Vivek Goyal
2007-07-26 15:44         ` Vivek Goyal
2007-07-26 15:47         ` Bernhard Walle
2007-07-26 15:47           ` Bernhard Walle
2007-07-26 15:54           ` Vivek Goyal
2007-07-26 15:54             ` Vivek Goyal
2007-07-26 16:14             ` Bernhard Walle
2007-07-26 16:14               ` Bernhard Walle
2007-07-26 16:21               ` Bernhard Walle
2007-07-26 16:21                 ` Bernhard Walle
2007-07-26 23:28             ` Takenori Nagano
2007-07-26 23:28               ` Takenori Nagano
2007-07-30  9:16               ` Vivek Goyal
2007-07-30  9:16                 ` Vivek Goyal
2007-07-30 13:42                 ` Eric W. Biederman
2007-07-30 13:42                   ` Eric W. Biederman
2007-07-31  5:55                   ` Takenori Nagano
2007-07-31  5:55                     ` Takenori Nagano
2007-07-31  6:53                     ` Eric W. Biederman
2007-07-31  6:53                       ` Eric W. Biederman
2007-08-01  9:26                       ` Takenori Nagano
2007-08-01  9:26                         ` Takenori Nagano
2007-08-01 10:00                         ` Eric W. Biederman
2007-08-01 10:00                           ` Eric W. Biederman
2007-08-02  8:11                           ` Takenori Nagano
2007-08-02  8:11                             ` Takenori Nagano
2007-08-02 11:28                           ` Vivek Goyal
2007-08-02 11:28                             ` Vivek Goyal
2007-08-03  4:05                             ` Keith Owens
2007-08-03  4:05                               ` Keith Owens
2007-08-03  6:25                               ` Andrew Morton
2007-08-03  6:25                                 ` Andrew Morton
2007-08-03  6:34                                 ` Keith Owens
2007-08-03  6:34                                   ` Keith Owens
2007-08-03  7:37                                   ` Andrew Morton
2007-08-03  7:37                                     ` Andrew Morton
2007-08-03  7:10                                 ` Eric W. Biederman
2007-08-03  7:10                                   ` Eric W. Biederman
2007-08-05 11:07                               ` Vivek Goyal
2007-08-05 11:07                                 ` Vivek Goyal
2007-08-14  8:34                                 ` Takenori Nagano
2007-08-14  8:34                                   ` Takenori Nagano
2007-08-14  8:37                                   ` Bernhard Walle
2007-08-14  8:37                                     ` Bernhard Walle
2007-08-14  8:48                                     ` Takenori Nagano
2007-08-14  8:48                                       ` Takenori Nagano
2007-08-14  8:53                                       ` Bernhard Walle
2007-08-14  8:53                                         ` Bernhard Walle
2007-08-14 13:24                                     ` Vivek Goyal
2007-08-14 13:24                                       ` Vivek Goyal
2007-08-16  9:26                                       ` Takenori Nagano
2007-08-16  9:26                                         ` Takenori Nagano
2007-08-16  9:45                                         ` Bernhard Walle
2007-08-16  9:45                                           ` Bernhard Walle
2007-08-17 10:56                                         ` Vivek Goyal
2007-08-17 10:56                                           ` Vivek Goyal
2007-08-21  7:45                                           ` Takenori Nagano [this message]
2007-08-21  7:45                                             ` Takenori Nagano
2007-08-23  3:52                                             ` Vivek Goyal
2007-08-23  3:52                                               ` Vivek Goyal
2007-08-21 13:18                                           ` Jay Lan
2007-08-21 13:18                                             ` Jay Lan
2007-08-21 13:21                                             ` Bernhard Walle
2007-08-21 13:21                                               ` Bernhard Walle
2007-08-23  3:56                                             ` Vivek Goyal
2007-08-23  3:56                                               ` Vivek Goyal
2007-08-23 17:34                                               ` Jay Lan
2007-08-23 17:34                                                 ` Jay Lan
2007-10-04 11:30                                                 ` Takenori Nagano

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=46CA97FE.90505@ah.jp.nec.com \
    --to=t-nagano@ah.jp.nec.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=vgoyal@in.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.