Re: [RFC] How drivers notice a MCA on I/O read? [1/3]

From: Jesse Barnes <>
Date: 2003-11-19 04:10:32
On Tue, Nov 18, 2003 at 07:11:20PM +0900, Hidetoshi Seto wrote:
> Assuming that Linux uses privilege level to determine action on MCA between
> kill the thread and down the system, if driver encounters MCA caused by I/O
> read, Linux should be down since privilege level of driver is kernel, not user.
> I want to convey the error to the offending driver, and want to enable the
> driver to retry failed read.

This would not only be useful for the occasional device failure, but
also for accessing memory spaces which by definition may or may not
respond to PIO requets, like legacy I/O bus and memory regions.  Upon
entering readb_check(), you could set a global telling the MCA handler
to potentially expect a failure from the address or range that was
passed in.  This would allow the MCA handler describe in simple terms
what went wrong in case of failure and/or take appropriate action.

> So, I think about a readb_check function that has checking ability
> enable it return error value if MCA occur on read.  Drivers could use
> readb_check instead of usual readb, and could diagnosis whether a
> retry be required or not, by the return value of readb_check.

Since this proposal would affect the driver API, it should probably be
discussed on  It may be beneficial to
other systems that hard fail under similar circumstances.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Tue Nov 18 12:13:12 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:20 EST