linux-mips
[Top] [All Lists]

a quick question regarding CONFIG_MIPS_UNCACHED..

To: linux-mips@linux-mips.org
Subject: a quick question regarding CONFIG_MIPS_UNCACHED..
From: "atul srivastava" <atulsrivastava9@rediffmail.com>
Date: 27 Nov 2002 09:11:14 -0000
Original-recipient: rfc822;linux-mips@linux-mips.org
Reply-to: "atul srivastava" <atulsrivastava9@rediffmail.com>
Sender: linux-mips-bounce@linux-mips.org
Hello,

Is it sufficient to set "CONFIG_MIPS_UNCACHED" in order to track a
possible cache related problem otherwise hard to debug.
in so many places the functions to operate on caches are called
directly..don't they should be placed under
"#ifdef CONFIg_MIPS_UNCACHED" , if not technically then at least
for consistent coding.

secondly if once i have gone for UNCACHED operation then dump_tlb_all should show the "page cheency attribute" for all entries as "UNCACHED" anywhere in whole address space..

in my case this attribute for some entries in TLB is still showing "Cacheable, noncoherent, write-through, no write allocate" ..how this is possible..

following is the relevant code:--

#ifdef CONFIG_MIPS_UNCACHED
        change_cp0_config(CONF_CM_CMASK, CONF_CM_UNCACHED);
#else
change_cp0_config(CONF_CM_CMASK, CONF_CM_CACHABLE_NONCOHERENT);
#endif

Best Regards,
Atul



<Prev in Thread] Current Thread [Next in Thread>