From: Tim Bird <tim.bird@am.sony.com>
To: Marc Andre Tanner <mat@brain-dump.org>
Cc: H Hartley Sweeten <hartleys@visionengravers.com>,
linux-embedded@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 7/7] printk: provide a filtering macro for printk
Date: Wed, 2 Sep 2009 10:31:53 -0700 [thread overview]
Message-ID: <4A9EAC09.7070000@am.sony.com> (raw)
In-Reply-To: <4A9EA5C9.3010900@am.sony.com>
Tim Bird wrote:
> Marc Andre Tanner wrote:
>> On Tue, Sep 01, 2009 at 07:32:25PM -0400, H Hartley Sweeten wrote:
>>> On Tuesday, September 01, 2009 4:24 PM, Tim Bird wrote:
>>>> Some places in the kernel break the message into pieces, like so:
>>>>
>>>> printk(KERN_ERR, "Error: first part ");
>>>> ...
>>>> printk(" more info for error.\n");
>>> Technically, shouldn't the second part of the message actually be:
>>>
>>> printk(KERN_CONT " more info for error.\n");
>>>
>>> Maybe some mechanism could be created to handle the continued message
>>> if they have the KERN_CONT?
>> Yes it's true that KERN_CONT isn't handled correctly, but I don't see a way
>> to change that.
>>
>>>> These parts would not be handled consistently under certain
>>>> conditions.
>>>>
>>>> It would be confusing to see only part of the message,
>>>> but I don't know how often this construct is used.
>> $ grep -R KERN_CONT linux-2.6 | wc -l
>> 373
>>
>>>> Maybe
>>>> another mechanism is needed to ensure that continuation
>>>> printk lines have the same log level as their start strings.
>> I currently don't see a way to achieve this with the CPP.
>
> If it's that few, then maybe it's OK to actually change
> the code for those printk statements. (Heck, these locations
> were all changed in the last 2 years anyway.)
>
> I'm just brainstorming here, but how about changing them from:
> printk(KERN_INFO "foo");
> printk(KERN_CONT "bar\n");
> to:
> printk(KERN_INFO "foo");
> printk_cont(KERN_INFO "bar\n");
>
> This way the continuation line has the log level, and can
> be conditionally compiled based on the VERBOSITY level. A little
> magic would be needed to strip the first 3 chars of the fmt
> string in printk_cont().
>
> I think this makes the printk messages a bit more consistent anyway,
> and still marks lines that are continuation lines.
Just another note. Detecting continuation lines also complicates
the printk timestamping code. If all continuation lines were
distinguishable by the printk code, then it might be possible
to simplify the timestamping code as a side effect of the
change.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2009-09-02 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1251844269-12394-1-git-send-email-mat@brain-dump.org>
[not found] ` <1251844269-12394-8-git-send-email-mat@brain-dump.org>
[not found] ` <4A9DAD2B.3080909@am.sony.com>
[not found] ` <BD79186B4FD85F4B8E60E381CAEE190901C55CD3@mi8nycmail19.Mi8.com>
[not found] ` <20090902130943.GE2736@debbook.brain-dump.org>
2009-09-02 17:05 ` [PATCH 7/7] printk: provide a filtering macro for printk Tim Bird
2009-09-02 17:31 ` Tim Bird [this message]
2009-09-02 18:22 ` H Hartley Sweeten
2009-09-04 14:05 ` Marc Andre Tanner
2009-09-10 9:22 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9EAC09.7070000@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=hartleys@visionengravers.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mat@brain-dump.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox