From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Borislav Petkov <bp@alien8.de>,
toshi.kani@hp.com, prarit@redhat.com, rafael.j.wysocki@intel.com,
isimatu.yasuaki@jp.fujitsu.com
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
fenghua.yu@intel.com, xen-devel@lists.xensource.com
Subject: Re: v3.9 - CPU hotplug and microcode earlier loading hits a mutex deadlock (x86_cpu_hotplug_driver_mutex)
Date: Wed, 8 May 2013 12:32:49 -0400 [thread overview]
Message-ID: <20130508163249.GB369@phenom.dumpdata.com> (raw)
In-Reply-To: <20130508142949.GC30955@pd.tnic>
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?
>
> 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.
> --
next prev parent reply other threads:[~2013-05-08 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 12:59 v3.9 - CPU hotplug and microcode earlier loading hits a mutex deadlock (x86_cpu_hotplug_driver_mutex) Konrad Rzeszutek Wilk
2013-05-07 19:00 ` Konrad Rzeszutek Wilk
2013-05-08 12:54 ` Borislav Petkov
2013-05-08 14:03 ` Konrad Rzeszutek Wilk
2013-05-08 14:29 ` Borislav Petkov
2013-05-08 15:20 ` H. Peter Anvin
2013-05-08 15:41 ` [Xen-devel] " Ross Philipson
2013-05-08 16:32 ` Konrad Rzeszutek Wilk [this message]
2013-05-08 18:19 ` Toshi Kani
2013-05-08 18:42 ` Konrad Rzeszutek Wilk
2013-05-08 18:59 ` Toshi Kani
2013-05-09 0:23 ` Rafael J. Wysocki
2013-05-08 16:13 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130508163249.GB369@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox