linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH,RFC] PPC32 Machine Check Handling
Date: Thu, 4 Nov 2004 12:08:05 -0700	[thread overview]
Message-ID: <20041104190805.GF13456@smtp.west.cox.net> (raw)
In-Reply-To: <20040827221204.GB30360@smtp.west.cox.net>

On Fri, Aug 27, 2004 at 03:12:04PM -0700, Tom Rini wrote:
> On Fri, Aug 27, 2004 at 11:26:29AM +0100, Adrian Cox wrote:
> > The attached patch rearranges PPC32 machine check handling in order to
> > test for internal CPU failures before signalling user processes. This
> > makes the behaviour match that of i386.
> >
> > The patch currently only changes behaviour for 6xx processors. It does
> > not enable any extra causes of machine check, but it will turn internal
> > CPU faults into kernel panics rather than signals.
> >
> > The PowerMac and Qspan specific code is moved into platform files. There
> > don't seem to be any boards in the tree that actually use Qspan PCI. I'd
> > like to hear test reports for PowerMac machines that take machine checks
> > on I/O faults.
> >
> > Paul, Tom: This isn't the finished version, but is there any chance of
> > something like this going mainstream?  The current behaviour makes it
> > very hard to separate chip failures and cooling problems from
> > application bugs.
> 
> This seems like a fine idea to me.

This get cleaned up anymore, etc?  Thanks.

-- 
Tom Rini
http://gate.crashing.org/~trini/

      parent reply	other threads:[~2004-11-04 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 10:26 [PATCH,RFC] PPC32 Machine Check Handling Adrian Cox
2004-08-27 22:12 ` Tom Rini
2004-08-28  0:38   ` Dan Malek
2004-11-04 19:08   ` Tom Rini [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=20041104190805.GF13456@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=adrian@humboldt.co.uk \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).