From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Disable external interrupts in bootwrapper
Date: Wed, 28 Mar 2007 18:52:33 +0200 [thread overview]
Message-ID: <f9bdca27dfc8ea20d0020261a5022ec4@kernel.crashing.org> (raw)
In-Reply-To: <1175041735.14065.37.camel@localhost.localdomain>
>>>> Disable external interrupts very early in the bootwrapper in case
>>>> the firmware left a device generating interrupts.
>>>
>>> Sounds reasonable, except that I wonder if systems running under a
>>> real OF want to do this...
>>
>> I don't know. Would someone who knows OF speak up?
>
> OF isn't supposed to use external interrupts
That isn't a hard rule. But yeah, hardly any OF
will ever use interrupts for normal operation --
the kernel can have taken control of the exception
vector and still want to access devices via OF, for
example.
> but I wouldn't bet on what
> Apple's one does... I think it's not safe to do that thus on OF based
> platforms.
Until you take control of the external interrupt and
decrementer interrupt (and overtemp interrupt, on
some CPUs), you really shouldn't turn off the EE bit
for extended periods of time.
Set EE=0 right before the earliest of a) you want OF
to be dead dead dead; or b) you copy the kernel's
exception vectors to 0; and all will be fine.
Segher
next prev parent reply other threads:[~2007-03-28 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 22:28 [PATCH] powerpc: Disable external interrupts in bootwrapper Mark A. Greer
2007-03-27 23:43 ` Paul Mackerras
2007-03-28 0:12 ` Mark A. Greer
2007-03-28 0:28 ` Benjamin Herrenschmidt
2007-03-28 1:03 ` Mark A. Greer
2007-03-28 1:26 ` David Gibson
2007-03-28 1:34 ` Mark A. Greer
2007-03-28 16:52 ` Segher Boessenkool [this message]
2007-03-28 1:05 ` Geoff Levand
2007-03-28 1:34 ` Mark A. Greer
2007-03-28 16:57 ` Segher Boessenkool
2007-04-10 22:37 ` Mark A. Greer
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=f9bdca27dfc8ea20d0020261a5022ec4@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@kernel.crashing.org \
--cc=paulus@samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).