From: Paul Mackerras <paulus@cs.anu.edu.au>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: bootstrap stuffs
Date: Tue, 16 Feb 1999 11:02:59 +1100 [thread overview]
Message-ID: <199902160002.LAA11648@tango.anu.edu.au> (raw)
In-Reply-To: <9902151757.AA75924@marc.watson.ibm.com> (message from David Edelsohn on Mon, 15 Feb 1999 12:57:34 -0500)
David Edelsohn <dje@watson.ibm.com> wrote:
> "isync" is used to discard instruction pre-fetch and ensure that
> all previous instructions have occurred. isync is not necessary for your
> situation either.
>
> As Gabriel correctly explained, a "sync" instruction may be
> necessary before interrupts are enabled if some off-chip operation, like
Sync and isync turn out to be needed on some revs of some chips
(particularly the 601) around rfi and mtmsr instructions.
(In fact the 601 seems to have another weird bug - in the hash_page
routine in head.S, the location of the rfi instruction w.r.t. cache
lines appears to be critical on the 601; if it's wrong, you get a
machine check on the rfi instruction. At one stage I found that with
2, 3, 6, or 7 nops added, it would work; with 0, 1, 4 or 5 nops added
it wouldn't. :-)
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-16 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-14 14:02 bootstrap stuffs Benjamin Herrenschmidt
1999-02-14 17:03 ` David Edelsohn
1999-02-14 18:58 ` Benjamin Herrenschmidt
1999-02-15 17:57 ` David Edelsohn
1999-02-15 18:20 ` Benjamin Herrenschmidt
1999-02-16 0:02 ` Paul Mackerras [this message]
1999-02-16 11:24 ` Gabriel Paubert
1999-02-16 11:44 ` Gabriel Paubert
1999-02-16 16:43 ` Geert Uytterhoeven
1999-02-16 17:39 ` Gabriel Paubert
1999-02-16 18:11 ` Benjamin Herrenschmidt
1999-02-17 6:23 ` Cort Dougan
[not found] <19990216134514.022163@mail.mipsys.com>
1999-02-16 13:18 ` Gabriel Paubert
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=199902160002.LAA11648@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.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).