From: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
To: "Edgar E. Iglesias" <edgar@axis.com>
Cc: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>,
qemu-devel@nongnu.org,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [Qemu-devel] sh: dcache flush breaks text region?
Date: Tue, 13 Jan 2009 03:57:22 +0100 [thread overview]
Message-ID: <20090113025722.GC30935@edgar.se.axis.com> (raw)
In-Reply-To: <20090111104259.GE26952@edgar.se.axis.com>
On Sun, Jan 11, 2009 at 11:42:59AM +0100, Edgar E. Iglesias wrote:
> On Sun, Jan 11, 2009 at 12:58:12PM +0900, Shin-ichiro KAWASAKI wrote:
> >
> > Edgar E. Iglesias wrote:
> >> Another solution might be for linux to use a ocpb followed by a ocpi insn
> >> on the line. IIUC that should achieve the same results net results.
> > I'm not sure about it. But I think we should not modify linux,
>
> I agree.
>
> The ocpb followed by the ocpi that I suggested won't work and I cant
> think of anything better than what linux is already doing.
I gave this some more thought and I think that there might be room for
improvements in the cache-sh4 flushing loops anyway.
The reason why the suggested ocbp+ocbi sequences didn't work was because
I later noticed that the same loop was beeing used for unconditional line
flushes aswell as for flushes for ranges where you actually know the
virtual addresses you want to flush (complete page flushes seem to be
treated differently).
If you separate the two, the flushes for virtual ranges can be done with
the ocbp+ocbi sequence. If I'm not misstaken, there are two main
advantages:
1. You will flush and invalidate much fewer lines, only those that
actually hit in the cache. This could turn out to be a pretty
significant win.
2. You get rid of the atomic requirements. It means you can do all the
ranged flushes with interrupts enabled all the time.
Best regards
next prev parent reply other threads:[~2009-01-13 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 17:38 [Qemu-devel] sh: dcache flush breaks text region? Shin-ichiro KAWASAKI
2009-01-10 19:53 ` Edgar E. Iglesias
2009-01-11 3:58 ` Shin-ichiro KAWASAKI
2009-01-11 10:42 ` Edgar E. Iglesias
2009-01-13 2:57 ` Edgar E. Iglesias [this message]
2009-01-12 12:58 ` Paul Mundt
2009-01-13 0:58 ` Edgar E. Iglesias
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=20090113025722.GC30935@edgar.se.axis.com \
--to=edgar.iglesias@axis.com \
--cc=edgar@axis.com \
--cc=kawasaki@juno.dti.ne.jp \
--cc=linux-sh@vger.kernel.org \
--cc=qemu-devel@nongnu.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).