LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: Takenori Nagano <t-nagano@ah.jp.nec.com>
Cc: vgoyal@in.ibm.com, Keith Owens <kaos@sgi.com>,
"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>
Subject: Re: [patch] add kdump_after_notifier
Date: Tue, 14 Aug 2007 10:37:10 +0200 [thread overview]
Message-ID: <20070814083710.GA14538@suse.de> (raw)
In-Reply-To: <46C1691E.7090708@ah.jp.nec.com>
* Takenori Nagano <t-nagano@ah.jp.nec.com> [2007-08-14 10:34]:
> Vivek Goyal wrote:
> > On Fri, Aug 03, 2007 at 02:05:47PM +1000, Keith Owens wrote:
> >
> >
> > To sum up, couple of options come to mind.
> >
> > - Register all the RAS tools on die notifier and panic
> > notifier lists with fairly high priority. Export list
> > of RAS tools to user space and allow users to decide the
> > order of execution and priority of RAS tools.
> >
> > - Create a separate RAS tool notifier list (ras_tool_notifer_list).
> > All the RAS tools register on this list. This list gets priority
> > over die or panic notifier list. User decides the oder of execution
> > of RAS tools.
> >
> > Here assumption is that above list will not be exported to modules.
> > All the RAS tools will be in kernel and they always get a priority
> > to inspect an event.
> >
> > What do others think?
>
> Very good idea. But there is a problem how to give default priority to RAS tools.
>
> How about priority changeable notifier_list? User can change list order
> dynamically if they want. Of course, we have to give highest priority to kdump
> by default. It is very useful for users who want to use some RAS tools.
I think that was the idea of the first “-” (“export list of RAS tools
to user space”).
Thanks,
Bernhard
next prev parent reply other threads:[~2007-08-14 8:37 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 [this message]
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
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=20070814083710.GA14538@suse.de \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=k-miyoshi@cb.jp.nec.com \
--cc=kaos@sgi.com \
--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).