From: "Kevin D. Kissell" <kevink@mips.com>
To: "Wayne Gowcher" <wgowcher@yahoo.com>, <linux-mips@linux-mips.org>
Subject: Re: Tips on inspecting / debuging cache
Date: Fri, 14 Mar 2003 09:22:13 +0100 [thread overview]
Message-ID: <001301c2ea02$d27a9bc0$10eca8c0@grendel> (raw)
In-Reply-To: 20030314021308.60082.qmail@web11905.mail.yahoo.com
> I am wondering if someone could point me towards
> articles / source code that would give me a little
> insight into how to debug cache problems in mips.
>
> For example , how do I inspect the contents of the
> cache ?
Which MIPS CPU are you using? The CACHE instruction
was introduced with the R4000 CPU as an implementation
dependent feature, and was finally standardized in the MIPS32
and MIPS64 architecture specs. See
http://www.mips.com/publications/processor_architecture.html
In MIPS32, to be able to properly inspect the cache, one needs
a CPU which implements the optional Index_Load_Tag CACHE
operation and has both TagHi/TagLo (required) DataHi/DataLo
(optional) registers. Pre-MIPS32 CPUs may offer the ability
to inspect the cache with variant mechanisms (see your chip
spec), or not at all.
>Are there routines to dump out the contents of
> the cache ?
People write them from time to time, but so far I don't
think anyone has written a "standard" cache dump API
or implementation in the Linux kernel.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Wayne Gowcher <wgowcher@yahoo.com>, linux-mips@linux-mips.org
Subject: Re: Tips on inspecting / debuging cache
Date: Fri, 14 Mar 2003 09:22:13 +0100 [thread overview]
Message-ID: <001301c2ea02$d27a9bc0$10eca8c0@grendel> (raw)
Message-ID: <20030314082213.R2DBhH4Wj0QSGUYmprvv5TKpku6aKg5a0MHCgfpGbqg@z> (raw)
In-Reply-To: 20030314021308.60082.qmail@web11905.mail.yahoo.com
> I am wondering if someone could point me towards
> articles / source code that would give me a little
> insight into how to debug cache problems in mips.
>
> For example , how do I inspect the contents of the
> cache ?
Which MIPS CPU are you using? The CACHE instruction
was introduced with the R4000 CPU as an implementation
dependent feature, and was finally standardized in the MIPS32
and MIPS64 architecture specs. See
http://www.mips.com/publications/processor_architecture.html
In MIPS32, to be able to properly inspect the cache, one needs
a CPU which implements the optional Index_Load_Tag CACHE
operation and has both TagHi/TagLo (required) DataHi/DataLo
(optional) registers. Pre-MIPS32 CPUs may offer the ability
to inspect the cache with variant mechanisms (see your chip
spec), or not at all.
>Are there routines to dump out the contents of
> the cache ?
People write them from time to time, but so far I don't
think anyone has written a "standard" cache dump API
or implementation in the Linux kernel.
Kevin K.
next prev parent reply other threads:[~2003-03-14 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 2:13 Tips on inspecting / debuging cache Wayne Gowcher
2003-03-14 8:22 ` Kevin D. Kissell [this message]
2003-03-14 8:22 ` Kevin D. Kissell
2003-03-14 19:26 ` Ralf Baechle
2003-03-14 21:53 ` Wayne Gowcher
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 23:23 Adam Kiepul
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='001301c2ea02$d27a9bc0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=wgowcher@yahoo.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