All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Rex Feany <RFeany@mrv.com>
Subject: Re: [PATCH 00/10] Fix 8xx MMU/TLB
Date: Wed, 18 Nov 2009 15:08:24 -0600	[thread overview]
Message-ID: <4B046248.7060101@freescale.com> (raw)
In-Reply-To: <OF735CB2F5.65B4E3F3-ONC1257671.002BB41C-C1257671.002C5E4F@transmode.se>

Joakim Tjernlund wrote:
> Scott Wood <scottwood@freescale.com> wrote on 17/11/2009 01:40:11:
>> No...  I only meant that the ITLB pinning got rid of the boot hang.
>>
>> When I mentioned the EFAULTs before you said, "No surprise as the it
>> seems like the DAR decoding is broken."  I thought you meant you'd found
>> a bug and fixed it in this respin.
> 
> Oh, there seems to be a misunderstanding here :)
> Lets go back a bit, you said some time ago:
> /Quote
>>> +3:   lwz   r11, 0(r11)		 /* Get the level 1 entry */
>>>       DO_8xx_CPU6(0x3b80, r3)
>>>       mtspr SPRN_MD_TWC, r11		 /* Load pte table base address */
>>>       mfspr r11, SPRN_MD_TWC		 /* ....and get the pte address */
>>>       lwz   r11, 0(r11)		 /* Get the pte */
>>>       /* concat physical page address(r11) and page offset(r10) */
>>>       rlwimi      r11, r10, 0, 20, 31
>> But r10 here contains SRR0 from above, and this is a data TLB error.
> 
> Never mind that last one, forgot that you'd be wanting to load the
> instruction. :-P
> 
> But the rlwimi is what's causing the machine checks.  I replaced it with:
> rlwinm		 r11, r11, 0, 0x3ffff000
> rlwimi		 r11, r10, 22, 0xffc
> 
> and things seem to work.  You could probably replace the rlwinm by
> subtracting PAGE_OFFSET from swapper_pg_dir instead.
> /End Quote
> 
> I read this as now everything is working, but I guess I misunderstood?
> You still have EFAULT here?

Ah, that one -- I don't recall whether it was fully working back then, or 
whether I just didn't notice the EFAULTs and was commenting more on the machine 
checks going away.

In the current patchset, it's "8xx: start using dcbX instructions in various 
copy routines" that introduces the problem.

-Scott

  reply	other threads:[~2009-11-18 21:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 17:09 [PATCH 00/10] Fix 8xx MMU/TLB Joakim Tjernlund
2009-11-15 17:09 ` [PATCH 01/10] 8xx: invalidate non present TLBs Joakim Tjernlund
2009-11-15 17:09   ` [PATCH 02/10] 8xx: Update TLB asm so it behaves as linux mm expects Joakim Tjernlund
2009-11-15 17:09     ` [PATCH 03/10] 8xx: Tag DAR with 0x00f0 to catch buggy instructions Joakim Tjernlund
2009-11-15 17:09       ` [PATCH 04/10] 8xx: Always pin kernel instruction TLB Joakim Tjernlund
2009-11-15 17:09         ` [PATCH 05/10] 8xx: Fixup DAR from buggy dcbX instructions Joakim Tjernlund
2009-11-15 17:09           ` [PATCH 06/10] 8xx: Add missing Guarded setting in DTLB Error Joakim Tjernlund
2009-11-15 17:09             ` [PATCH 07/10] 8xx: Restore _PAGE_WRITETHRU Joakim Tjernlund
2009-11-15 17:09               ` [PATCH 08/10] 8xx: start using dcbX instructions in various copy routines Joakim Tjernlund
2009-11-15 17:09                 ` [PATCH 09/10] 8xx: Remove DIRTY pte handling in DTLB Error Joakim Tjernlund
2009-11-15 17:09                   ` [PATCH 10/10] 8xx: DTLB Miss cleanup Joakim Tjernlund
2009-11-16 21:00 ` [PATCH 00/10] Fix 8xx MMU/TLB Scott Wood
2009-11-16 21:27   ` Scott Wood
2009-11-16 22:53     ` Joakim Tjernlund
2009-11-17  0:40       ` Scott Wood
2009-11-17  8:04         ` Joakim Tjernlund
2009-11-18 21:08           ` Scott Wood [this message]
2009-11-18 21:45             ` Joakim Tjernlund
2009-11-18 21:58               ` Scott Wood
2009-11-18 23:05                 ` Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2009-11-14 10:42 Joakim Tjernlund

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=4B046248.7060101@freescale.com \
    --to=scottwood@freescale.com \
    --cc=RFeany@mrv.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.