From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>, Olaf Hering <olh@suse.de>
Subject: Re: ppc32 PIO recovery mecanism
Date: Mon, 06 Nov 2006 12:20:47 +1100 [thread overview]
Message-ID: <1162776047.28571.268.camel@localhost.localdomain> (raw)
In-Reply-To: <1162775915.3415.2.camel@shinybook.infradead.org>
On Mon, 2006-11-06 at 09:18 +0800, David Woodhouse wrote:
> On Mon, 2006-11-06 at 11:41 +1100, Benjamin Herrenschmidt wrote:
> > On 32 bits powerpc, we currently have a mechanism where we try to
> > recover from machine checks happening on PIO operations (inb/outb/....).
> > This mecanisms has proven of dubious reliability in the past and it's my
> > understanding that we've pretty fixed all relevant legacy drivers that
> > distro typically load so that they don't muck around when they
> > shouldn't.
> >
> > I'm currently merging 32 and 64 bits io.h and I would really like to
> > just get rid of that stuff, but I'd like your distro point of view
> > first. Is this mechanism still useful at all or not ?
>
> Yes, I think it's still useful because there are some drivers which
> aren't update to use check_legacy_ioport() (or whatever other system)
> yet.
>
> Not many, mind you -- but I'd like to be 100% sure before we drop it.
> Let's start by making it print with KERN_CRIT instead of KERN_DEBUG?
We should rate limit if we do that tho... Some drivers will just totally
flood you.
I'll keep it around for now.
Ben.
next prev parent reply other threads:[~2006-11-06 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 0:41 ppc32 PIO recovery mecanism Benjamin Herrenschmidt
2006-11-06 1:18 ` David Woodhouse
2006-11-06 1:20 ` Benjamin Herrenschmidt [this message]
2006-11-06 6:11 ` Olaf Hering
2006-11-06 6:24 ` David Woodhouse
2006-11-06 6:25 ` Olaf Hering
2006-11-09 18:33 ` Olaf Hering
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=1162776047.28571.268.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.