All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
To: sparclinux@vger.kernel.org
Subject: Re: the late arch/sparc64/mm/init.c:__flush_cache_all
Date: Mon, 02 Feb 2004 18:51:38 +0000	[thread overview]
Message-ID: <87d68xco1x.fsf@uga.edu> (raw)
In-Reply-To: <87ektjdcu9.fsf@uga.edu>

"David S. Miller" <davem@redhat.com> writes:

...
> 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.

I re-read all the manual sections describing the cache features.  My
intention was to find something that would allow me to do benchmarks
on a process for which I could disable caching.

The i386 has wbinvd which makes the cache write dirty pages to memory
and invalidate all entries, but the ultrasparc doesn't seem to have
anything like that.  You can loop over addresses doing displacement
flushing, but you have to make sure that the addresses you use are
already in the TLB, and I'm not sure how that's being done in the
kernel. 

    8.2.3
    
    ... Care must be taken to ensure that the range of read-only
    addresses is mapped in the MMU before starting a displacement
    flush, otherwise the TLB miss handler may put new data into the
    caches.

The manual also says that there are different kinds of addresses,
cachable and non-cachable, but I don't see any way to say, "Make all
of the VA's in this process non-cachable."

-- 
--Ed L Cashin            |   PGP public key:
  ecashin@uga.edu        |   http://noserose.net/e/pgp/


  parent reply	other threads:[~2004-02-02 18:51 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
2004-02-02 18:51 ` Ed L Cashin [this message]
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=87d68xco1x.fsf@uga.edu \
    --to=ecashin@uga.edu \
    --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.