All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: sh: fix wrong icache/dcache address-array start addr in cache-debugfs.
Date: Mon, 06 Jun 2011 03:31:26 +0000	[thread overview]
Message-ID: <20110606033125.GE26101@linux-sh.org> (raw)
In-Reply-To: <4DE76654.40605@st.com>

On Fri, Jun 03, 2011 at 02:42:09PM +0100, Srinivas KANDAGATLA wrote:
> Hi Paul,
> My comments are in-lined.
> Paul Mundt wrote:
> >On Thu, Jun 02, 2011 at 11:30:44AM +0100, Srinivas KANDAGATLA wrote:
> >>This patch fixes a icache/dcache address-array start address while
> >>dumping its entires in debugfs. Perviously the code was attempting to
> >>remember the address in static variable, which is no more required
> >>for debugfs, as the function can be executed in one pass.
> >>
> >If the assertion that we can now do this in one pass is true then
> >certainly killing of the complexity/brokenness of caching the array can
> >be dropped. It's been many years since I wrote that code so I have
> >absolutely no recollection of the re-entry case, but it was necessary at
> >the time. 
> Could be that, the existing code was carried from non-seq_file style 
> interface (proc read...).

That sounds like the most probable case.

> >Also, what cache configurations have you tested this with? Our common
> >case is 4-way set associative 32kB dcache, which if memory serves was
> >already enough to overrun whatever debugfs had handy (I suppose a 4k
> >page, as with procfs).
> I did test on 2Way cache with 32KB icache/dcache system.
> Original issue is not do with overrun, but incorrect results in virtual 
> file.
> 
Good enough for me. Applied, thanks.

      parent reply	other threads:[~2011-06-06  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 10:30 sh: fix wrong icache/dcache address-array start addr in cache-debugfs Srinivas KANDAGATLA
2011-06-02 17:54 ` Paul Mundt
2011-06-03 13:42 ` Srinivas KANDAGATLA
2011-06-06  3:31 ` Paul Mundt [this message]

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=20110606033125.GE26101@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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.