All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: xen-devel@lists.xensource.com
Subject: SMP on the MacBook
Date: Wed, 09 Aug 2006 20:40:43 +0200	[thread overview]
Message-ID: <87d5b9bvmc.fsf@xs4all.nl> (raw)

Hi,

For a while now I have been trying to debug an issue with Xen on the
MacBook, doing this is part of my Summer of Code project to get Xen
working properly on the Intel Mac.  In case some of you don't know,
the MacBook is an Intel Core Duo based laptop from Apple, which lacks
some legacy hardware.

Xen (testing) works perfectly for me when starting it with "nosmp",
however when not using it, it crashes while starting up the second
core.  There have been some bug report on this issue already.

Below I will explain the problem in more detail and with some
observations.  I will be very grateful if someone can come up with
ideas of how to fix this or give me some ideas that can lead to a
solution.  Not only Xen has this problem, but so has FreeBSD and
NetBSD, so a solution will be beneficial to these projects as well.

What happens is the following: The first core sends two IPI
messages(INIT and STARTUP) to start the second core.  When the second
core is started, it notifies the first core of this so it can continue
with the boot process.  However, the second core is not started by
these messages, the loop that waits for the second core times out,
continues and Xen crashes.

One strange thing is that Xen initializes the second core properly
when you press a key on the keyboard after the IPIs are sent.  I am
expecting this interrupt somehow wakes up the second core so it can
accept and process the IPIs.  Because it is a laptop the second core
is put in deep sleep mode to save power in case an OS does not use
this core at all.  But as I understand it, it should wake up when an
INIT IPI arrives.

The problems I am having with Xen can be reproduced with linux when
booting with "acpi=ht", which means the ACPI interpreter is not
started.

Hopefully someone has some ideas how to deal with this issue and how
to properly fix this.  If you want more information or want me to test
things, feel free to ask.

Thanks,
Marco

             reply	other threads:[~2006-08-09 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 18:40 Marco Gerards [this message]
2006-08-10 14:04 ` SMP on the MacBook gimli
2006-08-10 14:34   ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2006-08-09 20:05 Ian Pratt
2006-08-09 20:41 ` Marco Gerards
2006-08-10  0:10 Ian Pratt
2006-08-10  8:25 ` Marco Gerards
2006-08-10 10:32 Ian Pratt

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=87d5b9bvmc.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.