Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takenori Nagano <t-nagano@ah.jp.nec.com>
To: Jay Lan <jlan@sgi.com>
Cc: k-miyoshi@cb.jp.nec.com, Bernhard Walle <bwalle@suse.de>,
	kexec@lists.infradead.org, vgoyal@in.ibm.com,
	"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: Thu, 04 Oct 2007 20:30:13 +0900	[thread overview]
Message-ID: <4704CEC5.3020306@ah.jp.nec.com> (raw)
In-Reply-To: <46CDC51D.5070206@sgi.com>

Hi all,

I finished to implement this function. I will send patches after this mail.
Please review them and give some comments.

Thanks,

Jay Lan wrote:
> Vivek Goyal wrote:
>> On Tue, Aug 21, 2007 at 06:18:31AM -0700, Jay Lan wrote:
>> [..]
>>>>>> 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?
>>>
>> I thought of couple of reasons.
>> - A very different syntax to modify the priority.
>> - Separate directories allow easy future extensions in terms of more
>>   files. For example, putting a small "description" file in each dir
>>   where each registered user can specify what does it do.
> 
> The first can be easily resolved by providing a comment section in the
> file with real examples. Users can simply uncomment a line to activate.
> But future expansion is certainly is a good reason for this layout.
> 
>> But I agree that a single file is good for consolidated view. As bernhard
>> suggested, may be we should also implement a read only file where one
>> will get a consolidated view.
> 
> Yep, this will help!
> 
>>> What do we decide priority if more than one component has
>>> the same priority value?
>>>
>> I think first come first serve would be appropriate in this case instead of
>> returning -EINVAL.
> 
> How does the kernel process the configuration files? By alphabetic order
> of the filename? Either way, i think a clear failure/warning dmesg is
> very important.
> 
> Thanks,
>  - jay
> 
>> Thanks
>> Vivek
>>
>> _______________________________________________
>> kexec mailing list
>> kexec@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/kexec
> 
> 


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

      reply	other threads:[~2007-10-04 11:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 12:15 [patch] add kdump_after_notifier 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
2007-08-21 13:21                                             ` Bernhard Walle
2007-08-23  3:56                                             ` Vivek Goyal
2007-08-23 17:34                                               ` Jay Lan
2007-10-04 11:30                                                 ` Takenori Nagano [this message]

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=4704CEC5.3020306@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=jlan@sgi.com \
    --cc=k-miyoshi@cb.jp.nec.com \
    --cc=kaos@ocs.com.au \
    --cc=kexec@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox