From: "wilbur.chan" <wilbur512@gmail.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: chelly wilbur <wilbur512@gmail.com>
Subject: Question about head_fsl_booke.S
Date: Sun, 26 Jul 2009 23:34:42 +0800 [thread overview]
Message-ID: <e997b7420907260834v5923326ele5af13713622c366@mail.gmail.com> (raw)
e500 , in head_fsl_booke.S
We know,the first two steps are:
1) invalidate all entries except the entry we are in
2) setup a temp mapping and jump to it respectively:
tlbwe
bl 1f
1: mflr r9
rlwimi r7,r9,0,20,31
addi r7, r7,24
mtspr SPRN_SRR0,r7
mtspr SPRN_SRR1,r6
rfi
/* jump to 0-4k .
question1: Why not this 'rfi' did not caused jumping into
4k-8k , or 10k-14k , etc ? */
li r6,0
question2: We know that, it is not allowed the two entrys having the
same EPN value,so, when setting up a temp entry which ranged from
0-4k, is it possible that , this
range(0-4k) may conflit with the entry we are executed in now?
Thx in advance.
regards,
next reply other threads:[~2009-07-26 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 15:34 wilbur.chan [this message]
2009-07-27 14:26 ` Question about head_fsl_booke.S Kumar Gala
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=e997b7420907260834v5923326ele5af13713622c366@mail.gmail.com \
--to=wilbur512@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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