[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130508142949.GC30955@pd.tnic>
Date: Wed, 8 May 2013 16:29:49 +0200
From: Borislav Petkov <bp@...en8.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, fenghua.yu@...el.com,
xen-devel@...ts.xensource.com
Subject: Re: v3.9 - CPU hotplug and microcode earlier loading hits a mutex
deadlock (x86_cpu_hotplug_driver_mutex)
On Wed, May 08, 2013 at 10:03:42AM -0400, Konrad Rzeszutek Wilk wrote:
[ … snip some funky BIOS code ]
> [here it shifts and continues on testing each CPU bit]
>
> > Questions over questions...?
>
> I probably went overboard with my answers :-)
Konrad, you're killing me! :-) You actually went and looked at the
BIOS disassembly voluntarily. You must be insane, I think you should
immediately go to the doctor now for a thorough checkup. :-)
I think I know who I can sling BIOS issues now to.
> > Looks like save_mc_for_early would need another, local mutex to fix that.
>
> Let me try that. Thanks for the suggestion.
Ok, seriously now: yeah, this was just an idea, it should at least get
the nesting out of the way.
About the BIOS deal: you're probably staring at some BIOS out there
but is this the way that it is actually going to be implemented on
the physical hotplug BIOS? I mean, I've only heard rumors about IVB
supporting physical hotplug but do you even have access to such BIOS to
verify?
All I'm saying is, let's not hurry too much before we actually can
really trigger this on baremetal.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists