From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753164AbdI1M0S (ORCPT ); Thu, 28 Sep 2017 08:26:18 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:43001 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753097AbdI1M0O (ORCPT ); Thu, 28 Sep 2017 08:26:14 -0400 Message-Id: <20170928121823.430053219@infradead.org> User-Agent: quilt/0.63-1 Date: Thu, 28 Sep 2017 14:18:23 +0200 From: Peter Zijlstra To: pmladek@suse.com, sergey.senozhatsky@gmail.com Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org, mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org Subject: [PATCH 0/3] printk: Add force_early_printk boot param Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Luckily many early_printk implementations are relatively sane and don't rely on anything much at all; the x86 early_serial_console for example is pure bit-banging without anything. So provide means to always use these and avoid the whole printk mess.