From: Marco Gerards <mgerards@xs4all.nl>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Disable SMP on the MacBook by default
Date: Thu, 14 Sep 2006 19:15:28 +0200 [thread overview]
Message-ID: <87venqtln3.fsf@xs4all.nl> (raw)
In-Reply-To: <C12F2A4B.1415%Keir.Fraser@cl.cam.ac.uk> (Keir Fraser's message of "Thu, 14 Sep 2006 15:48:27 +0100")
Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:
> On 13/9/06 23:11, "Marco Gerards" <mgerards@xs4all.nl> 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
appreciated.
Thanks,
Marco
prev parent reply other threads:[~2006-09-14 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 20:45 [PATCH] Disable SMP on the MacBook by default Marco Gerards
2006-09-13 20:57 ` Ian Pratt
2006-09-13 21:38 ` Marco Gerards
2006-09-13 21:38 ` Ian Pratt
2006-09-13 22:11 ` Marco Gerards
2006-09-13 22:19 ` gimli
2006-09-13 22:30 ` gimli
2006-09-13 22:39 ` Ian Pratt
2006-09-13 22:34 ` Marco Gerards
2006-09-14 14:48 ` Keir Fraser
2006-09-14 17:15 ` Marco Gerards [this message]
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=87venqtln3.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.