Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760115AbYHOPkE (ORCPT ); Fri, 15 Aug 2008 11:40:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756307AbYHOPjy (ORCPT ); Fri, 15 Aug 2008 11:39:54 -0400 Received: from mail-gx0-f16.google.com ([209.85.217.16]:47794 "EHLO mail-gx0-f16.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754041AbYHOPjx (ORCPT ); Fri, 15 Aug 2008 11:39:53 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=VswUhxCT69SZCAfEYgBIE0IlcPcz+cfx/qM71bQ79yi/Ivr3fnZ0YJ73pnQmebtP7Y yHPu9raa9COC57Wp5W2YNYGJLqOr4AUfHY92yk/J0hCO2IQwfYPQg5iJd7qvQbtQWGXT oOCPpByaX/FK0ki0tRbyXU64EwsKmh1T/CT5E= Message-ID: Date: Fri, 15 Aug 2008 08:39:52 -0700 From: "Tim Hockin" To: "Jan Blunck" Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros. Cc: "Greg KH" , "Joe Perches" , schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, lf_kernel_messages@lists.linux-foundation.org, "Andrew Morton" , "Michael Holzheu" , "Gerrit Huizenga" , "Randy Dunlap" , "Jan Kara" , "Pavel Machek" , "Sam Ravnborg" , "=?UTF-8?Q?Jochen_Vo=C3=9F?=" , "Kunai Takashi" , "Tim Bird" In-Reply-To: <20080815112117.GP10078@bolzano.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080730165656.118280544@de.ibm.com> <20080730171156.824640459@de.ibm.com> <1218733457.2651.11.camel@localhost> <1218769739.24527.76.camel@localhost> <20080815034419.GB803@suse.de> <20080815112117.GP10078@bolzano.suse.de> X-Google-Sender-Auth: dad47e446e2a8a93 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1811 Lines: 36 On Fri, Aug 15, 2008 at 4:21 AM, Jan Blunck wrote: > On Thu, Aug 14, Tim Hockin wrote: > >> On Thu, Aug 14, 2008 at 8:44 PM, Greg KH wrote: >> > >> > What is wrong with what we have already agreed to standardise on here >> > people? dev_printk() for devices! It uniquely shows the device, what >> > driver is bound to it (if any), the bus id, and everything else. >> >> Part of the problem, imho, is the "if any" part. But I am more than happy to >> build on existing solutions. All the world is not a dev, though. I'd like to >> be able to report something like an OOM kill in (roughly) the same way as an >> ATA error, and I want (though could be talked out of) a way to tell these >> "events" (for lack of a better word) apart from plain-old-printk()s. > > I don't think that he wants to unify all the printk's in the system. I don't > think that reporting all errors "in the same way as an ATA error" makes any > sense. That would just lead to very stupid and unnatural messages for all > errors that are not like "ATA errors". Annotation of existing errors is a much > more flexible and feasible solution to that problem. Please don't misinterpret. I don't want to make other errors parse like an ATA error, I want to make the plumbing be parallel. I want one umbrella mechanism for reporting things that are more important than just-another-printk(). Because frankly, "parse dmesg" is a pretty crappy way to have to monitor your system for failures, and I am tired of explaining to people why we still do that. Tim -- 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/