From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751424AbdJENmf (ORCPT ); Thu, 5 Oct 2017 09:42:35 -0400 Received: from merlin.infradead.org ([205.233.59.134]:36566 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751310AbdJENme (ORCPT ); Thu, 5 Oct 2017 09:42:34 -0400 Date: Thu, 5 Oct 2017 15:42:27 +0200 From: Peter Zijlstra To: Petr Mladek Cc: sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org, rostedt@goodmis.org, mingo@kernel.org, tglx@linutronix.de, Jason Wessel Subject: Re: [PATCH 1/3] printk: Fix kdb_trap_printk placement Message-ID: <20171005134227.zu5j6nic6cfgxcza@hirez.programming.kicks-ass.net> References: <20170928121823.430053219@infradead.org> <20170928122513.328354788@infradead.org> <20171005133844.GA16068@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171005133844.GA16068@pathway.suse.cz> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 05, 2017 at 03:38:44PM +0200, Petr Mladek wrote: > Or can the kdb console commands be called in NMI context? IIRC most of KDB runs from NMI context.