From: Ralf Baechle <ralf@linux-mips.org>
To: peter fuerst <post@pfrst.de>
Cc: naresh kamboju <naresh.kernel@gmail.com>, linux-mips@linux-mips.org
Subject: Re: cacheflush system call-MIPS
Date: Fri, 13 Feb 2009 23:56:03 +0000 [thread overview]
Message-ID: <20090213235603.GA32274@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0902140002180.408@Indigo2.Peter>
On Sat, Feb 14, 2009 at 12:50:46AM +0100, peter fuerst wrote:
> there is one more good reason to ... : the Impact Xserver needs to do
> a cacheflush(a,w,DCACHE) as part of the refresh-sequence.
> And hence requires a sys_cacheflush, let's say, more conforming to the
> man-page (or some disgusting new ioctl in the Impact kernel-driver to
> do an equivalent operation ;-)
Why does it need that flush?
Ralf
next prev parent reply other threads:[~2009-02-13 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 15:16 cacheflush system call-MIPS naresh kamboju
2009-02-11 13:16 ` Ralf Baechle
2009-02-13 23:50 ` peter fuerst
2009-02-13 23:56 ` Ralf Baechle [this message]
2009-02-15 2:20 ` peter fuerst
2009-02-17 17:06 ` David Daney
2009-02-17 19:45 ` Eugene Surovegin
2009-02-17 20:50 ` David VomLehn (dvomlehn)
2009-02-17 20:50 ` David VomLehn (dvomlehn)
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=20090213235603.GA32274@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=naresh.kernel@gmail.com \
--cc=post@pfrst.de \
/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