All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Buzov <vbuzov@ru.mvista.com>
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: Mon, 25 Jun 2007 18:09:33 +0400	[thread overview]
Message-ID: <467FCC9D.6010904@ru.mvista.com> (raw)
In-Reply-To: <3372b921591ca9731d2703f04e6c35f1@kernel.crashing.org>

Segher Boessenkool wrote:

>> Note that 745x processors have L3 cache installed and may have the same
>> problem requiring similar code modifications to use L3 hardware flushing
>> mechanism.
>
>
> What does the erratum say?

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.

>
> The L3 is a very different beast from the L2, IIRC it is
> a pure victim cache so it cannot have this problem at all?

I'm not sure if it is a pure victim cache. I read the MPC7450 reference 
manual and see that the L3 cache operates similarly to the L2. The main 
difference between those caches is that L3 uses an external SRAM memory 
while L2 is a pure on-chip cache.

Vlad.

>
>
> Segher
>

  reply	other threads:[~2007-06-25 14:09 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 [this message]
2007-06-28  8:24                 ` Segher Boessenkool
2007-06-28  9:13                   ` Benjamin Herrenschmidt
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=467FCC9D.6010904@ru.mvista.com \
    --to=vbuzov@ru.mvista.com \
    --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 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.