This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Disable SMP on the MacBook by default

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disable SMP on the MacBook by default
From: Marco Gerards <mgerards@xxxxxxxxx>
Date: Thu, 14 Sep 2006 19:15:28 +0200
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Sep 2006 10:09:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C12F2A4B.1415%Keir.Fraser@xxxxxxxxxxxx> (Keir Fraser's message of "Thu, 14 Sep 2006 15:48:27 +0100")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-copies-to: mgerards@xxxxxxxxx
References: <C12F2A4B.1415%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> writes:

> On 13/9/06 23:11, "Marco Gerards" <mgerards@xxxxxxxxx> wrote:
>> The second core can not be initialized because the INIT IPI does not
>> arrive.  It only happens on the MacBook and not on the desktop Intel
>> Macs.  On the MacBook the second core is put into deep sleep mode.  It
>> should get out of sleep mode when an IPI or interrupt is received.
>> That does not happen.  It looks like the keyboard interrupt does
>> wakeup the second core, after which the IPI is received.
> Have you tried tickling the second core with some interrupt or NMI IPIs from
> the boot core? Sounds like a slightly harder kick is required.

Yes I did try NMI IPIs, that did not have any effect.  IIRC I tried
generating interrupts using the APIC, but I do not remember if I
succeed, but if I did it didn't fix the problem.

Is there any other way I can have a look at to easily generate an
interrupt without causing weird side effects?

> What about tracing what the Linux ACPI interpreter kicks out in terms of
> hardware accesses? Perhaps you can work out what the ACPI goop actually does
> in low-level terms, which could then perhaps be applied in a simpler form
> (than ACPI interpreting) to Xen?

How would that work?  To be honest I do not know much about ACPI and
what's possible with it.  A few pointers to get me started is highly


Xen-devel mailing list