2010/11/19 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>: > On Fri, Nov 19, 2010 at 12:10 AM, Huang Ying <ying.huang@xxxxxxxxx> wrote: >> >> This is used by APEI ERST and GEHS. But it is a generic hardware >> error reporting mechanism and can be used by other hardware error >> reporting mechanisms such as EDAC, PCIe AER, Machine Check, etc. > > Yeah, no. > > Really. > > We don't want some specific hardware error reporting mechanism. > Hardware errors are way less common than other errors, so making > something that is special to them just isn't very interesting. Reading the following google paper on memory errors: http://www.google.com/research/pubs/pub35162.html I suppose they weren't really reporting memory errors with printk. Because of this: "The scale of the system and the data being collected make the analysis non-trivial. Each one of many ten-thousands of machines in the fleet logs every ten minutes hundreds of parameters, adding up to many TBytes." This would add up to gigabytes of generated data, for each machine, in some minutes. It seems to me that printk isn't really suited to report large amounts of raw data. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
