Re: v3.9 - CPU hotplug and microcode earlier loading hits a mutexdeadlock (x86_cpu_hotplug_driver_mutex)
From: Rafael J. Wysocki
Date: Wed May 08 2013 - 20:24:06 EST
On 5/8/2013 6:32 PM, Konrad Rzeszutek Wilk wrote:
On Wed, May 08, 2013 at 04:29:49PM +0200, Borislav Petkov wrote:
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.
Great .. :-)
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?
Unfortunatly not. I am getting an IvyTown box so hopefully that has this
support. But I thought that Fenghua did since he mentioned in the patch.
Besides that I think this can also appear on VMWare if one is doing
CPU hotplug and on some HP machines - let me CC the relevant people
extracted from drivers/acpi/processor_driver.c.
(see https://lkml.org/lkml/2013/5/7/588 for the thread)
Rafael, do you know of any specific Intel hardware that has this implemented?
No, I don't have this information.
By the way, here's a general request.
Please CC any messages having the word "ACPI" anywhere in the body or
subject to linux-acpi@xxxxxxxxxxxxxxxx I'm really tired of chasing
ACPI-related threads on the LKML just because people don't care about
CCing relevant lists and I'm going to NAK all patches touching ACPI in
any way if they haven't been CCed to the ACPI list. Seriously.
This particular item may or may not conflict with some ongoing work
taking place in there (and patches present in my tree).
And you've already had problems with ACPI-related code conflicts, so
that's not like it's never happened.
Thanks,
Rafael
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego,
numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
N‹§²æìr¸›yúèšØb²X¬¶ÇvØ^–)Þ{.nÇ+‰·¥Š{±‘êçzX§¶›¡Ü}©ž²ÆzÚ&j:+v‰¨¾«‘êçzZ+€Ê+zf£¢·hšˆ§~††Ûiÿûàz¹ ®w¥¢¸?™¨èÚ&¢)ßf”ù^jÇy§m…á@A«a¶Úÿ 0¶ìh®å’i