From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [PATCH v5 3/9] x86/head: Move early exception panic code into early_fixup_exception Date: Mon, 4 Apr 2016 08:36:35 -0700 Message-ID: <57028A03.3000902@linux.intel.com> References: <4085070316fc3ab29538d3fcfe282648d1d4ee2e.1459605520.git.luto@kernel.org> <20160402183919.GA2538@pd.tnic> <20160402204752.GC2538@pd.tnic> <20160404115206.GG8372@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , xen-devel , Borislav Petkov , X86 ML , Andrew Morton , Petr Mladek , KVM list , "linux-kernel@vger.kernel.org" , Linus Torvalds , Peter Zijlstra To: Andy Lutomirski , Jan Kara Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 4/4/2016 8:32 AM, Andy Lutomirski wrote: > > Adding locking would be easy enough, wouldn't it? > > But do any platforms really boot a second CPU before switching to real > printk? Given that I see all the smpboot stuff in dmesg, I guess real > printk happens first. I admit I haven't actually checked. adding locking also makes things more fragile in terms of getting the last thing out before you go down in flaming death.... until it's a proven problem, this early, get the message out at all is more important than getting it out perfectly, sometimes.