On Fri, Nov 19, 2010 at 11:52 PM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Nov 19, 2010 at 12:10 AM, Huang Ying <ying.huang@xxxxxxxxx> wrote: >> Normally, corrected hardware error records will go through the kernel >> processing and be logged to disk or network finally. ÂBut for >> uncorrected errors, system may go panic directly for better error >> containment, disk or network is not usable in this half-working >> system. ÂTo avoid losing these valuable hardware error records, the >> error records are saved into some kind of simple persistent storage >> such as flash before panic, so that they can be read out after system >> reboot successfully. > > I think this is totally the wrong thing to do. TOTALLY. > > The fact is, concentrating about "hardware errors" makes this > something that I refuse to merge. It's such an idiotic approach that > it's disgusting. > > Now, if this was designed to be a "hardware-backed persistent 'printk' > buffer", and was explicitly meant to save not just some special > hardware error, but catch all printk's (which may be due to hardware > errors or oopses or warnings or whatever), that would be useful. > > But limiting it to just some special source of errors makes this > pointless and not ever worth merging. Yes. APEI ERST can be used to back persistent 'printk', and that is in our plan too. But APEI ERST is not limited to do that, it can be used for printk, hardware error, and maybe some other users. When we design APEI ERST support, we have multiple users in mind. Best Regards, Huang Ying -- 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
