[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPXgP12fMp6+1UquRapLUP9+Ap0XPWnbChZvEEvcP54njCngZg@mail.gmail.com>
Date: Thu, 17 May 2012 17:23:14 +0200
From: Kay Sievers <kay@...y.org>
To: Sasha Levin <levinsasha928@...il.com>
Cc: greg@...ah.com, torvalds@...ux-foundation.org, mingo@...nel.org,
linux-kernel@...r.kernel.org, joe@...ches.com, hpa@...nel.org,
yinghai@...nel.org
Subject: Re: [RFC] printk: add relative printk timing support
On Thu, May 17, 2012 at 5:02 PM, Sasha Levin <levinsasha928@...il.com> wrote:
> This patch adds support for relative timestamps in printk output.
> Next, with Linus' suggestion (Month and date, no seconds):
>
> [May 17 14:13] foo
Any idea how to handle suspend cycles right? The wall clock time
translation might not be correct anymore, or is that covered?
Also, we currently record local CPU times, they are only guaranteed to
be monotonic for the same CPU, not across them. So we could see
negative offsets?
Kay
--
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