From: David Edelsohn <dje@watson.ibm.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Lou Langholtz <ldl@chpc.utah.edu>,
linuxppc-dev@lists.linuxppc.org, gdt@linuxppc.org,
cort@cs.nmt.edu
Subject: Re: linux-2.2.13pre15 stability w/ head.S patch
Date: Fri, 29 Oct 1999 14:11:16 -0400 [thread overview]
Message-ID: <9910291811.AA21080@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Gabriel Paubert <paubert@iram.es> of "Fri, 29 Oct 1999 12:34:30 +0200." <Pine.HPX.4.10.9910291132120.18743-100000@gra-ux1.iram.es>
>>>>> Gabriel Paubert writes:
Gabriel> OTOH when address translation is turned on (or when the its state is
Gabriel> unknown) I would have put an isync _before_ the first mtdbatu to make
Gabriel> sure that it does not interfere with previous instructions (this is
Gabriel> required from the manuals AFAICT).
You are correct, I mistyped the example. The isync's should go
before the entire block of DBAT updates and after. The PowerPC
Microprocessor Programming Environments book synchronization requirements
state that a "context-synchronizing instruction" is REQUIRED PRIOR and
REQUIRED AFTER a mtspr (DBAT) instruction. Context Synchronizing
Instructions are "sc", "rfi", "rfid", and "isync". Disabling the valid
bits by zeroing the upper BAT register before modifying the lower BAT
register is necessary.
If address translation is off, the context sychronization is
unnecessary.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-29 18:11 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
1999-10-29 10:34 ` Gabriel Paubert
1999-10-29 18:11 ` David Edelsohn [this message]
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=9910291811.AA21080@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 \
--cc=paubert@iram.es \
/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).