From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>, Olaf Hering <olh@suse.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: ppc32 PIO recovery mecanism
Date: Mon, 06 Nov 2006 11:41:34 +1100 [thread overview]
Message-ID: <1162773695.28571.260.camel@localhost.localdomain> (raw)
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 ?
Cheers,
Ben.
next reply other threads:[~2006-11-06 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 0:41 Benjamin Herrenschmidt [this message]
2006-11-06 1:18 ` ppc32 PIO recovery mecanism David Woodhouse
2006-11-06 1:20 ` Benjamin Herrenschmidt
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=1162773695.28571.260.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 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).