[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH v5 3/9] x86/head: Move early exception panic code into early_fixup_exception
- To: Andy Lutomirski <luto@xxxxxxxxxxxxxx>, Jan Kara <jack@xxxxxxx>
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
- Date: Mon, 4 Apr 2016 08:36:35 -0700
- Cc: KVM list <kvm@xxxxxxxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, X86 ML <x86@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Petr Mladek <pmladek@xxxxxxx>, xen-devel <Xen-devel@xxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 04 Apr 2016 15:36:47 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
