public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] I/O MCA recovery
Date: Tue, 04 May 2004 22:58:32 +0000	[thread overview]
Message-ID: <200405041558.32288.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200405040954.09524.jbarnes@engr.sgi.com>

On Tuesday, May 4, 2004 3:51 pm, David Mosberger wrote:
> Yes.  I doubt it would be an issue for inX/outX emulation in the int10
> module.

True.

> I was talking about hard-failure of inX/outX.  If SN2 does that, it's
> broken and I'm not terribly sympathetic (but see below).

But my point was: doesn't in/out hard fail on other ia64 platforms too?  If 
so, then it makes sense to deal with it generically.

>   Jesse> it's a generic way to deal with hard fails on PIO reads,
>   Jesse> which afaik, affects all ia64 platforms.  Correct me if I'm
>   Jesse> wrong here...
>
> Let me try to say it differently: inX/outX must soft-fail.  How you
> achieve that on SN2, I don't really care.  If, for other reasons,
> there happens to be an infrastructure you can hook into to facility
> implementation of soft-fail inX/outX on SN2, that's certainly fine by
> me.  But don't try to use inX/outX soft-fail as a reason to justify
> the infrastructure.  Better?

Sure, that makes sense.  The other part of the implementation was to deal with 
regular MMIO accesses though--userspace drivers want to get signalled when an 
error occurs, would you propose the page fault mechanism to detect that as 
well, or is an MCA handler a better way to go?

Thanks,
Jesse

  parent reply	other threads:[~2004-05-04 22:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04 16:54 [RFC] I/O MCA recovery Jesse Barnes
2004-05-04 17:14 ` Grant Grundler
2004-05-04 17:27 ` Jesse Barnes
2004-05-04 17:43 ` David Mosberger
2004-05-04 17:51 ` Grant Grundler
2004-05-04 18:04 ` Jesse Barnes
2004-05-04 18:07 ` Jesse Barnes
2004-05-04 18:20 ` David Mosberger
2004-05-04 22:36 ` Jesse Barnes
2004-05-04 22:50 ` Chris Wedgwood
2004-05-04 22:51 ` David Mosberger
2004-05-04 22:58 ` Jesse Barnes [this message]
2004-05-04 23:11 ` Grant Grundler
2004-05-04 23:13 ` David Mosberger
2004-05-04 23:15 ` David Mosberger
2004-05-04 23:17 ` Jesse Barnes
2004-05-04 23:18 ` Grant Grundler
2004-05-04 23:23 ` Alex Williamson
2004-05-04 23:31 ` Grant Grundler
2004-05-04 23:31 ` David Mosberger
2004-05-04 23:36 ` Grant Grundler
2004-05-12 19:03 ` Jesse Barnes
2004-05-12 21:11 ` David Mosberger
2004-05-12 21:24 ` Jesse Barnes
2004-05-12 21:35 ` David Mosberger
2004-05-12 21:44 ` Jesse Barnes
2004-05-12 21:52 ` Jesse Barnes
2004-05-12 21:54 ` David Mosberger
2004-05-12 21:59 ` Jesse Barnes
2004-05-13  9:02 ` Luck, Tony
2004-05-13 15:52 ` Jesse Barnes
2004-05-13 16:07 ` Luck, Tony
2004-05-13 16:43 ` Russ Anderson
2004-05-13 16:53 ` Jesse Barnes

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=200405041558.32288.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.kernel.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