From: Scott Wood <scottwood@freescale.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Rex Feany <RFeany@mrv.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/6] PowerPc 8xx TLB/MMU fixes
Date: Mon, 05 Oct 2009 16:31:58 -0500 [thread overview]
Message-ID: <4ACA65CE.3070406@freescale.com> (raw)
In-Reply-To: <OFFC147C60.2DA4B63D-ONC1257646.00733843-C1257646.0073CFFD@transmode.se>
Joakim Tjernlund wrote:
> Yes, every ld.so uses dcbX and icbi insn when relocatin code.
> Maybe you see some version of the dcbX bug, but my fault.c should
> fix them up. My bet would be the 32 byte cache line, it will miss
> out every second line and so the results are unreliable.
I found the 32-byte stuff from an objdump; it looks like there's a
runtime check for the cache line size that avoids running that code if
it's different.
-Scott
next prev parent reply other threads:[~2009-10-05 21:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 12:16 [PATCH 0/6] PowerPc 8xx TLB/MMU fixes Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 1/6] 8xx: DTLB Error must check for more errors Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 2/6] 8xx, fault: Add some debug code to do_page_fault() Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 3/6] 8xx: get rid of _PAGE_HWWRITE dependency in MMU Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 4/6] 8xx: Tag DAR with 0x00f0 to catch buggy instructions Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 5/6] 8xx: Fixup DAR from buggy dcbX instructions Joakim Tjernlund
2009-10-05 12:16 ` [PATCH 6/6] 8xx: start using dcbX instructions in various copy routines Joakim Tjernlund
2009-10-05 20:17 ` [PATCH 3/6] 8xx: get rid of _PAGE_HWWRITE dependency in MMU Benjamin Herrenschmidt
2009-10-05 21:25 ` Joakim Tjernlund
2009-10-05 21:37 ` Benjamin Herrenschmidt
2009-10-05 22:00 ` Joakim Tjernlund
2009-10-05 22:09 ` Benjamin Herrenschmidt
2009-10-05 22:55 ` Joakim Tjernlund
2009-10-05 23:15 ` Benjamin Herrenschmidt
2009-10-05 23:35 ` Joakim Tjernlund
2009-10-06 0:34 ` Benjamin Herrenschmidt
2009-10-06 6:15 ` Joakim Tjernlund
2009-10-06 6:45 ` Benjamin Herrenschmidt
2009-10-06 7:54 ` Joakim Tjernlund
2009-10-06 15:40 ` Joakim Tjernlund
2009-10-06 17:28 ` Joakim Tjernlund
2009-10-06 22:05 ` Joakim Tjernlund
2009-10-06 23:25 ` Benjamin Herrenschmidt
2009-10-07 1:07 ` Benjamin Herrenschmidt
2009-10-07 7:47 ` Joakim Tjernlund
2009-10-05 18:12 ` [PATCH 0/6] PowerPc 8xx TLB/MMU fixes Scott Wood
2009-10-05 18:27 ` Joakim Tjernlund
2009-10-05 20:09 ` Scott Wood
2009-10-05 21:04 ` Joakim Tjernlund
2009-10-05 21:31 ` Benjamin Herrenschmidt
2009-10-05 21:41 ` Joakim Tjernlund
2009-10-05 21:46 ` Scott Wood
2009-10-05 21:31 ` Scott Wood [this message]
2009-10-05 22:04 ` Rex Feany
2009-10-05 22:31 ` Joakim Tjernlund
2009-10-05 22:37 ` Benjamin Herrenschmidt
2009-10-05 22:58 ` Joakim Tjernlund
2009-10-05 23:49 ` Joakim Tjernlund
2009-10-06 1:52 ` Benjamin Herrenschmidt
2009-10-06 8:06 ` Joakim Tjernlund
2009-10-06 8:32 ` Benjamin Herrenschmidt
2009-10-06 10:58 ` Joakim Tjernlund
2009-10-06 11:06 ` Benjamin Herrenschmidt
2009-10-06 11:39 ` Joakim Tjernlund
2009-10-06 13:18 ` Joakim Tjernlund
2009-10-05 22:42 ` Rex Feany
2009-10-05 23:00 ` Joakim Tjernlund
2009-10-06 6:25 ` Joakim Tjernlund
2009-10-06 6:44 ` Benjamin Herrenschmidt
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=4ACA65CE.3070406@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.