From: David Edelsohn <dje@watson.ibm.com>
To: Lou Langholtz <ldl@chpc.utah.edu>
Cc: linuxppc-dev@lists.linuxppc.org, gdt@linuxppc.org, cort@cs.nmt.edu
Subject: Re: linux-2.2.13pre15 stability w/ head.S patch
Date: Thu, 28 Oct 1999 13:39:04 -0400 [thread overview]
Message-ID: <9910281739.AA35624@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Lou Langholtz <ldl@chpc.utah.edu> of "Thu, 28 Oct 1999 12:06:02 MDT." <3818908A.8A6539B6@chpc.utah.edu>
The general, conservative procedure that should be followed for
any BAT change is:
li rX, 0
mtdbatu N, rX
isync
mtdbatl N, rL
mtdbatu N, rU
isync
I do not see the posted assembly code performing any isync's to prevent
speculation. mtspr does not produce complete serialization in the
pipeline, and the serialization is implementation-dependent.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-28 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-28 18:06 linux-2.2.13pre15 stability w/ head.S patch Lou Langholtz
1999-10-28 17:39 ` David Edelsohn [this message]
1999-10-29 10:34 ` Gabriel Paubert
1999-10-29 18:11 ` David Edelsohn
1999-10-29 3:24 ` Cort Dougan
1999-10-29 18:13 ` Lou Langholtz
1999-10-30 3:58 ` Martin Costabel
1999-10-30 15:07 ` Takashi Oe
1999-10-30 18:36 ` phandel
1999-10-31 20:31 ` Geert Uytterhoeven
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=9910281739.AA35624@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=cort@cs.nmt.edu \
--cc=gdt@linuxppc.org \
--cc=ldl@chpc.utah.edu \
--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).