From: "kang shuo" <blackfin.kang@gmail.com>
To: galak@kernel.crashing.org
Cc: linuxppc-embedded@ozlabs.org.
Subject: ask two question about e500 implementation in arch/ppc/kernel/head_fsl_booke.S
Date: Wed, 11 Jul 2007 18:21:08 +0800 [thread overview]
Message-ID: <a7f827420707110321scea22beg9505286e00ba79b2@mail.gmail.com> (raw)
hi,galak:
I have two question about e500 part of linux kernel. I
can not get reponse from maillist . So I sent the questions to you
directly.
1. in arch/ppc/kernel/head_fsl_booke.S
603 FIND_PTE
604 andi. r13, r11, _PAGE_PRESENT /* Is the page present? */
605 beq 2f /* Bail if not present */
That seems _PAGE_PRESENT should be set before enter DataTLBError
exception handler(Or the following finish_tlb_load function will not
execute), but in __ioremap function of e500 implementation,
_PAGE_PRESENT bit is not set for an io address map.Why?
2. still in arch/ppc/kernel/head_fsl_booke.S
791 #ifdef CONFIG_E200
792 /* Round robin TLB1 entries assignment */
793 mfspr r12, SPRN_MAS0
794
795 /* Extract TLB1CFG(NENTRY) */
796 mfspr r11, SPRN_TLB1CFG
797 andi. r11, r11, 0xfff
798
799 /* Extract MAS0(NV) */
800 andi. r13, r12, 0xfff
801 addi r13, r13, 1
802 cmpw 0, r13, r11
803 addi r12, r12, 1
804
805 /* check if we need to wrap */
806 blt 7f
807
808 /* wrap back to first free tlbcam entry */
809 lis r13, tlbcam_index@ha
810 lwz r13, tlbcam_index@l(r13)
811 rlwimi r12, r13, 0, 20, 31
812 7:
813 mtspr SPRN_MAS0,r12
814 #endif /* CONFIG_E200 */
815
816 tlbwe
That seems original tlb entry will be overwritten in the above code
for e500? Why , I thought a free tlb entry should be select and fill
for e500. Just like CONFIG_E200.
-- Thanks
-- Michael.Kang
next reply other threads:[~2007-07-11 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 10:21 kang shuo [this message]
2007-07-11 13:41 ` ask two question about e500 implementation in arch/ppc/kernel/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=a7f827420707110321scea22beg9505286e00ba79b2@mail.gmail.com \
--to=blackfin.kang@gmail.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@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;
as well as URLs for NNTP newsgroup(s).