From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ladislav Michl <ladis@psi.cz>, linux-mips@oss.sgi.com
Subject: Re: [patch] linux: DBE/IBE handling rewrite
Date: Wed, 26 Jun 2002 14:05:52 +0200 [thread overview]
Message-ID: <20020626140552.F19858@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020626121553.23599A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Wed, Jun 26, 2002 at 01:51:08PM +0200
On Wed, Jun 26, 2002 at 01:51:08PM +0200, Maciej W. Rozycki wrote:
> > This way, the fixup search is invoked first and a system-specific handler
> > can judge whether to let the fixup be invoked or a serious failure
> > happened and the system should act appropriately. The handler can do
> > whatever actions are needed (e.g. clear error status data in system
> > registers, report ECC syndromes, etc.) for the system for both cases.
>
> OK, here is the code. I wrote it a bit differently from what I
> considered yesterday, as fixup doesn't seem useful for a system-specific
> handler. With the following code only a boolean flag is passed informing
> whether a fixup is available and the handler can decide how to treat an
> error, based on the state passed as arguments and possibly additional one
> obtained from system-specific resources. Both MIPS and MIPS64 are handled
> in the same way. For MIPS64 it means a removal of duplicated similar code
> as well. I adjusted some SGI-specific code appropriately, but platform
> maintainers will have to check if bus_error_init() stubs are OK for them.
>
> Ralf, OK to apply?
Certainly looks saner than what we're having right now. Please apply.
Ralf
next prev parent reply other threads:[~2002-06-26 12:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 11:33 DBE/IBE handling incompatibility Ladislav Michl
2002-06-19 16:47 ` Maciej W. Rozycki
2002-06-25 0:36 ` Ladislav Michl
2002-06-25 11:55 ` Maciej W. Rozycki
2002-06-26 11:51 ` [patch] linux: DBE/IBE handling rewrite Maciej W. Rozycki
2002-06-26 12:05 ` Ralf Baechle [this message]
2002-06-26 13:07 ` Maciej W. Rozycki
2002-06-26 17:21 ` Jun Sun
2002-06-27 12:00 ` Maciej W. Rozycki
2002-06-27 17:12 ` Jun Sun
2002-06-27 18:29 ` Maciej W. Rozycki
2002-06-27 19:08 ` Jun Sun
2002-06-27 20:00 ` Maciej W. Rozycki
2002-06-26 20:59 ` [patch] GIO bus support Ladislav Michl
2002-06-26 23:46 ` Ralf Baechle
2002-06-27 10:14 ` FIR problem jeff
2002-06-27 10:14 ` jeff
2002-06-27 12:21 ` [patch] GIO bus support Maciej W. Rozycki
2002-08-04 22:03 ` Ladislav Michl
2002-09-28 19:55 ` Ladislav Michl
2002-06-26 17:17 ` [patch] linux: DBE/IBE handling rewrite Jun Sun
2002-06-27 11:51 ` Maciej W. Rozycki
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=20020626140552.F19858@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=ladis@psi.cz \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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