[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+1xoqf5YbkOJgQJWOgck0NpqGzGtxtHHJASZKHvwVuBzkKK6A@mail.gmail.com>
Date: Sat, 12 May 2012 09:43:57 +0200
From: Sasha Levin <levinsasha928@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Kay Sievers <kay@...y.org>, Greg KH <gregkh@...uxfoundation.org>,
Yinghai Lu <yinghai@...nel.org>, Joe Perches <joe@...ches.com>,
Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length
record buffer
On Fri, May 11, 2012 at 5:47 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> Btw, I'd also *love* to see some model (eventually - not necessarily
> now) where we could have the option of the time printouts being a bit
> different (rather than just on/off). It would be very nice if we had
> "relative" time printouts for events close together, so the rule could
> be something like:
>
> - if time is same as last line, pad with empty
>
> - if time is more than a minute from last one, show an absolute value
> of dd hh:mm:ss
>
> - otherwise, show a relative value of +ss.mmmmmm
>
> So the on/off choice could be on/off/relative.
>
> Hmm?
So I got something like this:
# sleep 61 ; echo foo > /dev/kmsg ; sleep 61 ; echo bar > /dev/kmsg ;
sleep 5 ; echo zoot > /dev/kmsg ; sleep 10 ; echo foo > /dev/kmsg ;
echo bar > /dev/kmsg ; sleep 61 ; echo zoot > /dev/kmsg ; echo foo >
/dev/kmsg
[ 673.222632] foo
[ 734.315249] bar
[ +5.077527] zoot
[ +10.235225] foo
[ +0.002971] bar
[ 810.883085] zoot
[ +0.003081] foo
If that looks right, I can send a patch once this printf overhaul is
stable, unless Kay already plans on doing it as part of his work.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists