All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.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, 08 May 2013 08:20:31 -0700	[thread overview]
Message-ID: <518A6D3F.4040405@zytor.com> (raw)
In-Reply-To: <20130508142949.GC30955@pd.tnic>

On 05/08/2013 07:29 AM, 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.
> 

Nah, that was just the ACPI AML.  Real BIOS code is much scarier.

	-hpa


  reply	other threads:[~2013-05-08 15:21 UTC|newest]

Thread overview: 16+ 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 [this message]
2013-05-08 15:41         ` [Xen-devel] " Ross Philipson
2013-05-08 15:41           ` Ross Philipson
2013-05-08 16:32         ` Konrad Rzeszutek Wilk
2013-05-08 18:19           ` Toshi Kani
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-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=518A6D3F.4040405@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=fenghua.yu@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.