[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171128144500.190aa85c@gandalf.local.home>
Date: Tue, 28 Nov 2017 14:45:00 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Mark Salyzyn <salyzyn@...roid.com>
Cc: Prarit Bhargava <prarit@...hat.com>,
Petr Mladek <pmladek@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...uxfoundation.org>,
Ingo Molnar <mingo@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Joe Perches <joe@...ches.com>
Subject: Re: [RFC patch 7/7] timekeeping: Hack to use fine grained
timestamps during boot
On Tue, 28 Nov 2017 11:10:02 -0800
Mark Salyzyn <salyzyn@...roid.com> wrote:
> There is no guarantee of sequential order of delivery for kernel prints.
But isn't the timestamp taken with the logbuf_lock, and then delivered
to the printk buffer? That would guarantee that all events will be in
order, and the timestamps be sequential. They are serialized by the
logbuf_lock.
-- Steve
Powered by blists - more mailing lists