Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	"Kevin D. Kissell" <kevink@mips.com>,
	linux-mips@oss.sgi.com, Michael Shmulevich <michaels@jungo.com>
Subject: Re: User applications
Date: Mon, 8 Jan 2001 14:30:14 -0200	[thread overview]
Message-ID: <20010108143014.E886@bacchus.dhis.org> (raw)
In-Reply-To: <3A59E978.873182CB@mips.com>; from carstenl@mips.com on Mon, Jan 08, 2001 at 05:23:20PM +0100

On Mon, Jan 08, 2001 at 05:23:20PM +0100, Carsten Langgaard wrote:

> What we need is a mechanism to partial invalidate the I-cache and a mechanism
> to write-back and/or invalidate the D-cache.

There is this nice little man page which should even be installed on your
Linux/Inhell box:


CACHEFLUSH(2)       Linux Programmer's Manual       CACHEFLUSH(2)


NAME
       cacheflush  -  flush  contents  of instruction and/or data
       cache

SYNOPSIS
       #include <asm/cachectl.h>

       int cacheflush(char *addr, int nbytes, int cache);

DESCRIPTION
       cacheflush flushes contents of indicated cache(s) for user
       addresses  in the range addr to (addr+nbytes-1). Cache may
       be one of:

       ICACHE Flush the instruction cache.

       DCACHE Write back to memory and  invalidate  the  affected
              valid cache lines.

       BCACHE Same as (ICACHE|DCACHE).


RETURN VALUE
       cacheflush  returns 0 on success or -1 on error. If errors
       are detected, errno will indicate the error.

ERRORS
       EINVAL cache parameter is not one of  ICACHE,  DCACHE,  or
              BCACHE.

       EFAULT Some   or   all   of  the  address  range  addr  to
              (addr+nbytes-1) is not accessible.


BUGS
       The current implementation ignores  the  addr  and  nbytes
       parameters.   Therefore always the whole cache is flushed.

NOTE
       This system call is only available on MIPS based  systems.
       It should not be used in programs intended to be portable.
















Linux 2.0.32                27 June 95                          1

  reply	other threads:[~2001-01-08 16:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08  9:40 User applications Carsten Langgaard
2001-01-08 13:30 ` Michael Shmulevich
2001-01-08 13:52   ` Carsten Langgaard
2001-01-08 14:14   ` Kevin D. Kissell
2001-01-08 14:14     ` Kevin D. Kissell
2001-01-08 14:16     ` Carsten Langgaard
2001-01-08 16:03       ` Ralf Baechle
2001-01-08 15:07     ` Maciej W. Rozycki
2001-01-08 15:21       ` Kevin D. Kissell
2001-01-08 15:21         ` Kevin D. Kissell
2001-01-08 15:40         ` Maciej W. Rozycki
2001-01-08 16:27           ` Ralf Baechle
2001-01-08 16:43             ` Maciej W. Rozycki
2001-01-08 16:41               ` Ralf Baechle
2001-01-08 16:05       ` Ralf Baechle
2001-01-08 16:23         ` Carsten Langgaard
2001-01-08 16:30           ` Ralf Baechle [this message]
2001-01-08 16:50             ` Carsten Langgaard
2001-01-08 17:56               ` Maciej W. Rozycki
2001-01-08 16:40           ` Maciej W. Rozycki
2001-01-08 17:42             ` Ralf Baechle
2001-01-08 17:58               ` Maciej W. Rozycki
2001-01-09 11:49                 ` Michael Shmulevich
2001-01-09 12:15                   ` Geert Uytterhoeven
2001-01-09 12:17                   ` Alan Cox
2001-01-09 12:17                     ` Alan Cox
2001-01-09 13:00                   ` Maciej W. Rozycki
2001-01-08 16:34         ` Maciej W. Rozycki
2001-01-08 14:16   ` Maciej W. Rozycki
2001-01-08 16:25 ` Ralf Baechle

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=20010108143014.E886@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=michaels@jungo.com \
    /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