From: Randy Dunlap <randy.dunlap@oracle.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: pete@bluelane.com, Jason Wessel <jason.wessel@windriver.com>,
Matt Mackall <mpm@selenic.com>,
Amit Kale <amitkale@linsyssoft.com>,
Dave Anderson <anderson@redhat.com>,
kdb@oss.sgi.com, jlan@sgi.com, Vivek Goyal <vgoyal@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kexec Mailing List <kexec@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: My position on general ``RAS'' tool support infrastructure
Date: Mon, 17 Sep 2007 18:38:53 -0700 [thread overview]
Message-ID: <20070917183853.42f29393.randy.dunlap@oracle.com> (raw)
In-Reply-To: <m1abrq7lbt.fsf@ebiederm.dsl.xmission.com>
On Thu, 13 Sep 2007 07:21:10 -0600 Eric W. Biederman wrote:
> Pete/Piet Delaney <pete@bluelane.com> writes:
>
> > Jason, Eric:
> >
> > Did you read Keith Owens suggestion on RAS tools from:
Yes. and I re-read it.
There are several things in Keith's email that make sense:
a. all RAS tools should use a common interface
b. it's not the kernel's job to decide which RAS tool runs first
Eric makes some good points too. I'm mostly similar to Eric:
paranoid about trusting software/hardware after a panic (or oops).
So if someone wants to use multiple RAS tools on a panic event,
enabling an admin to set priorities is OK with me, but I'll only
trust the first one that is used, and even that one may have
problems. IOW, I don't see a big need to support multiple RAS
tools at one time. (speaking for myself)
> So if someone who is suggesting an implementation can absorb
> and understand the requirements of the different groups and come
> up with solutions that meet the requirements of the different projects
> I think progress can be made. That as far as I know takes talent.
Ack that.
---
~Randy
next prev parent reply other threads:[~2007-09-18 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46E8B06D.9080006@bluelane.com>
2007-09-13 13:21 ` Eric W. Biederman
2007-09-18 1:38 ` Randy Dunlap [this message]
2007-09-18 4:28 ` Vivek Goyal
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=20070917183853.42f29393.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=amitkale@linsyssoft.com \
--cc=anderson@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jason.wessel@windriver.com \
--cc=jlan@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pete@bluelane.com \
--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
all inboxes | Powered by JetHome®