From: Vladislav Buzov <vbuzov@ru.mvista.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC/PATCH] powerpc: MPC7450 L2 HW cache flush feature utilization
Date: Thu, 28 Jun 2007 14:47:15 +0400 [thread overview]
Message-ID: <468391B3.3080100@ru.mvista.com> (raw)
In-Reply-To: <1183022026.5521.269.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
>>>The erratum says nothing about any HW bugs with L3 cache flush. I just
>>>mentioned that the L3 cache flush operation described in MPC7450
>>>Reference manual is similar to the L2 using the L3 cache hardware
>>>flushing mechanism. For instance, it requires a complete L3 locking
>>>before flushing.
>>>
>>>
>>Then I think we should use that mechanism in the Linux kernel.
>>Anything else is waiting for bugs to bite.
>>
>>
>
>I just figured out ... we actually already have all of that cache flush
>code :-) I wrote most of it in fact. It's just that for some (bad)
>reasons, it's somewhat hidden in arch/powerpc/platforms/powermac/cache.S
>
>So I think best would be to take it from there and make it more
>generic ...
>
>
I'm just wondering who is supposed to do that. I can copy the code from
cache.S to l2cr_6xx.S and test it on 7448 since I have only this
processor on hand. So, I can't test the L3.
I've looked through cache.S and see it contains a dcbf loop over 4Mb
along with L2, L3 HW cache flushing. The comments says 'Due to a bug
with the HW flush on some CPU revs, we occasionally experience data
corruption...'. Could you please clarify which CPU revisions have this
bug and whether it is the same bug described in errata and requiring a
complete cache locking before flushing? Do we still need to use the dcbf
loop in _set_L2CR() for MPC7450 processors?
Thanks,
Vlad.
>Cheers,
>Ben.
>
>
>
>
next prev parent reply other threads:[~2007-06-28 10:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 10:19 [RFC/PATCH] powerpc: MPC7450 L2 HW cache flush feature utilization Vladislav Buzov
2007-06-14 13:56 ` Segher Boessenkool
2007-06-14 17:12 ` Vladislav Buzov
2007-06-14 22:26 ` Mark A. Greer
2007-06-15 8:16 ` Segher Boessenkool
2007-06-15 8:55 ` Vladislav D. Buzov
2007-06-15 9:01 ` Segher Boessenkool
2007-06-15 9:33 ` Vladislav D. Buzov
2007-06-15 10:44 ` Segher Boessenkool
2007-06-15 8:14 ` Segher Boessenkool
2007-06-15 8:42 ` Vladislav D. Buzov
2007-06-15 8:56 ` Segher Boessenkool
2007-06-15 21:20 ` Mark A. Greer
2007-06-15 22:14 ` Segher Boessenkool
2007-06-21 12:37 ` Benjamin Herrenschmidt
2007-06-22 15:22 ` Vladislav Buzov
2007-06-23 15:46 ` Segher Boessenkool
2007-06-25 14:09 ` Vladislav Buzov
2007-06-28 8:24 ` Segher Boessenkool
2007-06-28 9:13 ` Benjamin Herrenschmidt
2007-06-28 10:47 ` Vladislav Buzov [this message]
2007-06-28 11:09 ` Benjamin Herrenschmidt
2007-06-25 19:00 ` Vladislav Buzov
2007-06-28 8:35 ` Segher Boessenkool
2007-06-29 10:41 ` Vladislav Buzov
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=468391B3.3080100@ru.mvista.com \
--to=vbuzov@ru.mvista.com \
--cc=benh@kernel.crashing.org \
--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.