Messages in this thread | | | From | Dave Peterson <> | Subject | Re: [PATCH] EDAC: core EDAC support code | Date | Mon, 13 Mar 2006 11:31:14 -0800 |
| |
On Friday 10 March 2006 23:18, Arjan van de Ven wrote: > > ok, perhaps things might look something like this? > > <snip> > > sounds like overdesign to me ;)
Hmm... ok :) I don't want to suggest that Linux's hardware error handling mechanism should be "all of the above". Rather my intent is this:
- To summarize some previously mentioned options for error handling APIs, and mention a couple more ideas. More discussion is needed to decide exactly what we want.
- To suggest that drivers and hardware subsystems may want some flexibility in how they detect and process errors. (However, there is also such a thing as too much flexibility; EDAC should create a certain amount of uniformity)
- To state a couple of motivations for keeping error checking (i.e. reading error info from registers and clearing the registers) logically separate from error handling (i.e. doing something with the info obtained from the registers)
Another thing to think about: If EDAC is going to collect error info from subsystems and drivers, it needs some sort of API that supports this. Although I don't think this requires anything fancy, it still needs some discussion.
I'd be curious to read more discussion/ideas about error handling APIs (and see some patches that illustrate the ideas).
Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |