From: richardliu@ms1.techarea.org (Richard Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: Change ARM Cache Type from Write-Back Cached Write Allocate to Write-Back, No Allocate
Date: Mon, 19 Apr 2010 11:09:11 +0800 [thread overview]
Message-ID: <4BCBC957.90302@ms1.techarea.org> (raw)
Based on ARM11 MPCore TRM r1p0
Page 5-16
At TLB table, TEX cache memory support 4 type cache types
1) Noncachabled
2) Write-Back cached Write Allocate, Buffered
3) Write-Through cached, No Allocate on Write, Buffered
4) Write-Back cached, No Allocate on Write, Buffered.
From ARM's information, if change the TEX type to Write-Through,
the L1 Cache would be "behavior is noncacheable"
I think we can disable L1/L2 cache to reach the same result.
If want to change the default setting from "Write-Back cached Write
Allocate, Buffered" to "Write-Back cached, No Allocate on Write, Buffered".
How to modify the build_mem_type_table in file mmu.c?
And should it need more patches on others part like L1 or L2 coherence
function?
next reply other threads:[~2010-04-19 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 3:09 Richard Liu [this message]
2010-04-19 7:18 ` Change ARM Cache Type from Write-Back Cached Write Allocate to Write-Back, No Allocate Russell King - ARM Linux
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=4BCBC957.90302@ms1.techarea.org \
--to=richardliu@ms1.techarea.org \
--cc=linux-arm-kernel@lists.infradead.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