linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@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 19:13:46 +1000	[thread overview]
Message-ID: <1183022026.5521.269.camel@localhost.localdomain> (raw)
In-Reply-To: <ce09df5afe642e8f6e9a576306cc1e41@kernel.crashing.org>


> > 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 ...

Cheers,
Ben.

  reply	other threads:[~2007-06-28  9:13 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 [this message]
2007-06-28 10:47                     ` Vladislav Buzov
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=1183022026.5521.269.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).