From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mauro Carvalho Chehab Subject: Re: Hardware Error Kernel Mini-Summit Date: Wed, 19 May 2010 08:54:39 -0300 Message-ID: <4BF3D17F.5000605@redhat.com> References: <4BF2392A.9040409@jp.fujitsu.com> <4BF2C3D1.10009@redhat.com> <1274204560.17703.82.camel@Joe-Laptop.home> <20100518185305.GA23921@elte.hu> <987664A83D2D224EAE907B061CE93D53C61D1C57@orsmsx505.amr.corp.intel.com> <20100518191802.GG25224@aftab> <20100518222832.GJ22675@basil.fritz.box> <20100519064619.GA30320@aftab> <20100519070919.GA9618@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100519070919.GA9618@elte.hu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bluesmoke-devel-bounces@lists.sourceforge.net To: Ingo Molnar Cc: Hidetoshi Seto , "Luck, Tony" , "Young, Brent" , Linux Kernel Mailing List , Borislav Petkov , "bluesmoke-devel@lists.sourceforge.net" , Andi Kleen , "Eric W. Biederman" , Doug Thompson , Joe Perches , Thomas Gleixner , Linux Edac Mailing List , Ingo Molnar , Matt Domsch List-Id: edac.vger.kernel.org Ingo Molnar wrote: > Regarding dmesg, there's a WIP patch on lkml that > integrates printks into this framework as well - makes > each printk also available as a special string event. > > That way a tool can have both programmatic access to > printk output (without having to interact with the syslog > buffer itself) - together with all the other structured > log sources, while humans can also see what is happening. Some system admins prefer to have everything on dmesg, as they can enable a serial console, and catch the logs remotely, even when the machine crashes for example due to a hardware failure. So, IMHO, one feature that the perf event needs is the capability to report errors via a serial console also, or a mechanism where some events are sent via dmesg. -- Cheers, Mauro ------------------------------------------------------------------------------