From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754171AbdK1TpE (ORCPT ); Tue, 28 Nov 2017 14:45:04 -0500 Received: from mail.kernel.org ([198.145.29.99]:57056 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752410AbdK1TpD (ORCPT ); Tue, 28 Nov 2017 14:45:03 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 075212187C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Tue, 28 Nov 2017 14:45:00 -0500 From: Steven Rostedt To: Mark Salyzyn Cc: Prarit Bhargava , Petr Mladek , Thomas Gleixner , LKML , Linus Torvalds , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Andrew Morton , Sergey Senozhatsky , Joe Perches Subject: Re: [RFC patch 7/7] timekeeping: Hack to use fine grained timestamps during boot Message-ID: <20171128144500.190aa85c@gandalf.local.home> In-Reply-To: <26f1d1fd-ed65-73d1-8278-8058b6b83a3e@android.com> References: <20171115181531.322572387@linutronix.de> <20171115182657.703928462@linutronix.de> <20171123125823.gnhwtnx6bxd3tb4q@pathway.suse.cz> <205229e2-fab4-31cb-60cd-f36bc2228804@redhat.com> <26f1d1fd-ed65-73d1-8278-8058b6b83a3e@android.com> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 28 Nov 2017 11:10:02 -0800 Mark Salyzyn 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