Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756397AbaFYKBz (ORCPT ); Wed, 25 Jun 2014 06:01:55 -0400 Received: from cantor2.suse.de ([195.135.220.15]:35284 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752745AbaFYKBy (ORCPT ); Wed, 25 Jun 2014 06:01:54 -0400 Date: Wed, 25 Jun 2014 12:01:49 +0200 (CEST) From: Jiri Kosina To: Konstantin Khlebnikov cc: =?ISO-8859-15?Q?Petr_Ml=E1dek?= , Steven Rostedt , Linux Kernel Mailing List , Linus Torvalds , Ingo Molnar , Andrew Morton , Michal Hocko , Jan Kara , Frederic Weisbecker , Dave Anderson Subject: Re: [RFC][PATCH 0/3] x86/nmi: Print all cpu stacks from NMI safely In-Reply-To: Message-ID: References: <20140619213329.478113470@goodmis.org> <20140619185810.4137e14b@gandalf.local.home> <20140619191923.1365850a@gandalf.local.home> <20140619193635.1949b469@gandalf.local.home> <20140620143525.GB8769@pathway.suse.cz> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 24 Jun 2014, Konstantin Khlebnikov wrote: > Originally I thought that seizing all cpus one by one and printing from > the initiator is a best approach and I've started preparing arguments > against over-engineered printk... By "seizing" I guess you mean sending IPI, right? What do you do if you'd interrupt it in the middle of printk() in order not to deadlock by trying to take the buffer lock on the initiator CPU? -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/