From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754264AbcJYEo6 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 25 Oct 2016 00:44:58 -0400
Received: from mail-pf0-f195.google.com ([209.85.192.195]:35842 "EHLO
        mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752105AbcJYEo5 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 25 Oct 2016 00:44:57 -0400
Date: Tue, 25 Oct 2016 13:44:52 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Joe Perches <joe@perches.com>,
        Geert Uytterhoeven <geert@linux-m68k.org>,
        Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Petr Mladek <pmladek@suse.cz>, Tejun Heo <tj@kernel.org>,
        Calvin Owens <calvinowens@fb.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux.git: printk() problem
Message-ID: <20161025044452.GA411@swordfish>
References: <CA+55aFwOBR6z55r2abAT_TuYTHfyuc8f75B2+Z7+Lhr9fzSZRA@mail.gmail.com>
 <CA+55aFzm6RpkaiDzS_q3J=4_hykCCgAZLjEf5nffgSZjUpQ17A@mail.gmail.com>
 <20161024140845.GA626@swordfish>
 <CA+55aFwNU_ggMjguqFNHpY6r4UmsLuu3-rXKoNRi8umRNCRJQw@mail.gmail.com>
 <CA+55aFy7+6YgT9oZwO6xRBYiWh6uxmx7-=uV4X2xcAt9dswBZQ@mail.gmail.com>
 <20161025015554.GA495@swordfish>
 <CA+55aFyDxSd0j7n5ZZgui07Qg1JN-Xm-dtS=oGikM3y0VZ+qHQ@mail.gmail.com>
 <CA+55aFwKYnrMJr_vSE+GfDGszeUGyd=CPUD15-zZ8yWQW61GBA@mail.gmail.com>
 <20161025040617.GA565@swordfish>
 <CA+55aFzW5YEXBy3hyrML5P87_FmQ_MDCDAodDwge6zwOOp9zkw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFzW5YEXBy3hyrML5P87_FmQ_MDCDAodDwge6zwOOp9zkw@mail.gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On (10/24/16 21:15), Linus Torvalds wrote:
[..]
> No. Most cont lines never hit the delay, because when the line is
> completed, it is flushed (and then printed synchronously, assuming it
> can get the console lock).
> 
> So the timeout only ever comes into effect if the line isn't completed
> in time at all. Which is actually very rare, and never happens for the
> "let's print things out in multiple chinks because we're using a
> loop".
> 
> Similarly, if a new printk() happens due to interleaving, the previous
> buffered line is always flushed first, so buffering never causes
> out-of-order behavior.

thanks. the patch works fine on my x86 box.

> Basically, the only time the timer actually does anything is if
> something just does a printk() without a newline, and no other
> printouts happen for the next 0.1s.

ok. perhaps, like slow serial console. will test on arm board later.

	-ss