From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1317BB88 for ; Mon, 19 Jun 2017 16:26:55 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5FEA713A for ; Mon, 19 Jun 2017 16:26:54 +0000 (UTC) Date: Mon, 19 Jun 2017 12:26:51 -0400 From: Steven Rostedt To: Andrew Lunn Message-ID: <20170619122651.57ba27c4@gandalf.local.home> In-Reply-To: <20170619152055.GM3786@lunn.ch> References: <20170619052146.GA2889@jagdpanzerIV.localdomain> <20170619103912.2edbf88a@gandalf.local.home> <20170619152055.GM3786@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] printk redesign List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 19 Jun 2017 17:20:55 +0200 Andrew Lunn wrote: > > 4) All other kernel information that's not critical at all, and perhaps > > doesn't even need to be serialized. At least, not against the above. > > This could be cached, and outputted at a later time than when the > > printk() was called. > > Developers machine probably have different requirements to production > machines. When debugging during code development, i want the debug > output to be in the correct order, independent of the level. If you > are going to cause reordering, you might want to add a sequence number > to each output, so it is possible to put it back into the correct > order. And it needs to be clear when output is out of order. Perhaps a kernel command line option could force this. -- Steve