From: jbarnes@sgi.com (Jesse Barnes)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Fri, 16 Jan 2004 17:21:00 +0000 [thread overview]
Message-ID: <20040116172100.GA13553@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401152057380.2631@evo.osdl.org>
On Thu, Jan 15, 2004 at 09:00:10PM -0800, Linus Torvalds wrote:
> If you care about machine check errors, use a special interface for that.
> A _really_ special one. Especially as on many systems you'll likely have
> to read status registers etc (and clear them before doing the IO) to see
> the errors.
>
> So that way you can get errors working, AND it won't actually make normal
> code any uglier.
How about one that allows you to register an error handling function for
a given address range and/or device? That would cover both read() and
write() cases, and would be optional so drivers wouldn't be forced to
become more complicated.
Jesse
WARNING: multiple messages have this Message-ID (diff)
From: jbarnes@sgi.com (Jesse Barnes)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, jeremy@sgi.com
Subject: Re: [PATCH] readX_relaxed interface
Date: Fri, 16 Jan 2004 09:21:00 -0800 [thread overview]
Message-ID: <20040116172100.GA13553@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401152057380.2631@evo.osdl.org>
On Thu, Jan 15, 2004 at 09:00:10PM -0800, Linus Torvalds wrote:
> If you care about machine check errors, use a special interface for that.
> A _really_ special one. Especially as on many systems you'll likely have
> to read status registers etc (and clear them before doing the IO) to see
> the errors.
>
> So that way you can get errors working, AND it won't actually make normal
> code any uglier.
How about one that allows you to register an error handling function for
a given address range and/or device? That would cover both read() and
write() cases, and would be optional so drivers wouldn't be forced to
become more complicated.
Jesse
next prev parent reply other threads:[~2004-01-16 17:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:49 [PATCH] readX_relaxed interface Jesse Barnes
2004-01-15 20:49 ` Jesse Barnes
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:16 ` Grant Grundler
2004-01-15 22:56 ` Jesse Barnes
2004-01-15 22:56 ` Jesse Barnes
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 3:19 ` Jeremy Higdon
2004-01-16 0:32 ` Greg KH
2004-01-16 0:32 ` Greg KH
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 2:21 ` Jesse Barnes
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 5:00 ` Linus Torvalds
2004-01-16 17:21 ` Jesse Barnes [this message]
2004-01-16 17:21 ` Jesse Barnes
2004-01-16 5:00 ` Grant Grundler
2004-01-16 5:00 ` Grant Grundler
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 9:31 ` Hironobu Ishii
2004-01-19 18:18 ` Grant Grundler
2004-01-19 18:18 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
2004-01-16 5:50 ` Grant Grundler
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=20040116172100.GA13553@sgi.com \
--to=jbarnes@sgi.com \
--cc=greg@kroah.com \
--cc=jeremy@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=torvalds@osdl.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 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.