From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751945AbdI1QCh (ORCPT ); Thu, 28 Sep 2017 12:02:37 -0400 Received: from mail-pg0-f68.google.com ([74.125.83.68]:34573 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750951AbdI1QCg (ORCPT ); Thu, 28 Sep 2017 12:02:36 -0400 X-Google-Smtp-Source: AOwi7QAY6iCnBk5bq7Vkgrd3Z6yfhK5mixqa0rR1nrcpFq3IVDmm0pcfhh4n9F7zMj1aR0NPZYGScw== Date: Fri, 29 Sep 2017 01:02:30 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: pmladek@suse.com, sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org, rostedt@goodmis.org, mingo@kernel.org, tglx@linutronix.de Subject: Re: [PATCH 0/3] printk: Add force_early_printk boot param Message-ID: <20170928160230.GA606@tigerII.localdomain> References: <20170928121823.430053219@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170928121823.430053219@infradead.org> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (09/28/17 14:18), Peter Zijlstra wrote: > Most all printk() bits are terminally broken because they rely on the scheduler > and blocking locks to function, making them unsuitable for debugging the > scheduler and NMI context things. hold on... wait a second... the scheduler is not lockless yet? darn... ok, I think having something like that in printk.c wouldn't hurt. Petr was going to take a look, IIRC. but what's up with that scheduler thing I keep hearing about, must be something new, can I disable it in kconfig? it seems to be conflicting with CONFIG_PRINTK. -ss