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: Marco Gerards <mgerards@xxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Disable SMP on the MacBook by default
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 14 Sep 2006 15:48:27 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 14 Sep 2006 07:47:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87fyevzaae.fsf@xxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbYDNYbFPUP8kQAEduN2wAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] Disable SMP on the MacBook by default
User-agent: Microsoft-Entourage/

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.

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?

 -- Keir

Xen-devel mailing list