linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bootstrap stuffs
Date: Sun, 14 Feb 1999 12:03:40 -0500	[thread overview]
Message-ID: <9902141703.AA37524@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Benjamin Herrenschmidt <bh40@calva.net> of "Sun, 14 Feb 1999 15:02:35 +0100." <19990214150235.030449@smtp.calvacom.fr>


>>>>> Benjamin Herrenschmidt writes:

>> Are all of those "sync" instructions necessary in your code?

Benjamin> Just paranoid. They were added around the interrupt switching to make
Benjamin> sure to sync an eventual second processor and everything else before
Benjamin> switching the MMU off. I beleive that for disabling the MMU, andi. is
Benjamin> probably more efficient than my ori/andc pair, could you just explain my
Benjamin> why you added &0xffff at it ?

	"andi." only operates on halfword, so one needs to make sure that
the constant is valid or the assembler will complain.  (~ 0x8000) will
produce values in the upper half of the 32-bit word.  PowerPC immediate
instructions apply to either the upper-half or lower-half of a 32-bit
word. 

	For correctness, "sync" must be used, but for best performance,
"sync" should be used sparingly, only when necessary.

	Michael's comment about the -mrelocatable flag are a more detailed
answer to your question.

David

[[ 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 ]]

  reply	other threads:[~1999-02-14 17:03 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 [this message]
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
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=9902141703.AA37524@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=bh40@calva.net \
    --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).