From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: linux-mips@linux-mips.org
Subject: Some cache questions
Date: Mon, 27 Dec 2004 17:35:07 +0100 [thread overview]
Message-ID: <41D039BB.3030202@enix.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Hello,
I'm using an RM9000 dual-core processor, buggy revisions (the one that
doesn't support the "Shared" cache state if I understood correctly).
When going through the CVS logs, I saw that Ralf quite recently changed
the cache mode from 4 to 5 in pgtable-bits.h. Is that change involved in
the use of the "Shared" cache state with newer RM9000 revisions that
don't have the bug ?
Currently, the KSEG0 cache coherency mode (2 lower bits of the CONFIG
register) is set to 3 during PMON (start.S file). When I write something
to the memory through KSEG0 with the first core, it doesn't appear to be
read by the second core. This indicates, in my opinion, that the cache
line of the first core hasn't been written to memory so that the second
core could use it. Am I right ?
If I want to correctly use both cores using KSEG0, should I set the mode
in the CONFIG register to 4 (so that I can work with buggy processors) ?
Thanks,
Thomas
--
PETAZZONI Thomas - thomas.petazzoni@enix.org
http://thomas.enix.org - Jabber: thomas.petazzoni@jabber.dk
http://kos.enix.org, http://sos.enix.org
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2004-12-27 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 16:35 Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 22:11 Some cache questions Brad Larson
2004-12-28 4:02 ` Manish Lachwani
2004-12-28 8:21 ` Thomas Petazzoni
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=41D039BB.3030202@enix.org \
--to=thomas.petazzoni@enix.org \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox