All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: the late arch/sparc64/mm/init.c:__flush_cache_all
Date: Wed, 28 Jan 2004 21:46:47 +0000	[thread overview]
Message-ID: <20040128134647.16e09369.davem@redhat.com> (raw)
In-Reply-To: <87ektjdcu9.fsf@uga.edu>

On Wed, 28 Jan 2004 15:42:38 -0500
Ed L Cashin <ecashin@uga.edu> wrote:

> My first question is why the function was removed.  With Seth Arnold's
> help, I found the patch at bkbits.net that removes __flush_cache_all,
> but the only clue is the subject header, "[SPARC64]: vmap/vunmap cache
> flushing need not do anything."  I don't really understand why the
> function was removed.

Because we no longer need to flush the whole thing in the kernel
any more, only specific addresses.

> Can use flushw_all and flush g6 to clear the dcache, icache, and
> ecache?

No, flushw_all() flushes the cpu register windows and "flush g6" flushes
one cacheline in the instruction cache.

Please download the UltraSPARC programmers manual from, for example:

	http://www.sun.com/processors/manuals/805-0087.pdf

to learn how to program the chip.


> Also, and less important---in __flush_cache_all's inline asm, I
> expected the percent sign to be escaped, as in the other init.c
> functions.  Why is there only one percent sign?
> 
> -- 
> --Ed L Cashin            |   PGP public key:
>   ecashin@uga.edu        |   http://noserose.net/e/pgp/
> 
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-01-28 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 20:42 the late arch/sparc64/mm/init.c:__flush_cache_all Ed L Cashin
2004-01-28 21:46 ` David S. Miller [this message]
2004-02-02 18:51 ` Ed L Cashin
2004-02-02 19:02 ` David S. Miller

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=20040128134647.16e09369.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=sparclinux@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.