• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 2946 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting 'shareable' attribute in PT entry discard cache policies ?

Sujith K V
Note: This was originally posted on 21st March 2012 at http://forums.arm.com

Hi,

I am working on Cortex-A8 with MMU Enabled.

I am configuring L1 as Write Through No Write Allocate and L2 as Write Back Write Allocate. Both L1 and L2 caches are enabled.

And the memory attribute is given normal memory and  'shareable'  in the page table entry.

Then, When I write to a variable, its also written to memory.

When I change only the memory attribute to 'non-shareable', the variable is written to cache only.

Is shareability attribute means, irrespective of the cache attributes we set, it will be 'write through ??', Or all writes are happening to memory only?

I dont see any other CP15 register settings which can cause this behaviour.

Can anyone help me ?

Regards,




Parents
  • Note: This was originally posted on 21st March 2012 at http://forums.arm.com

    In general, cache policies are defined in the ARM ARM as "wishful thinking". The processor implementation may ignore them under certain conditions.
    Declaring a region as non-shareable means that no other master in the system will access that region. From the processor core's perspective it makes no difference whether the actual cache behavior is write-through (as configured) or write back.

    Kind regards
    Marcus
Reply
  • Note: This was originally posted on 21st March 2012 at http://forums.arm.com

    In general, cache policies are defined in the ARM ARM as "wishful thinking". The processor implementation may ignore them under certain conditions.
    Declaring a region as non-shareable means that no other master in the system will access that region. From the processor core's perspective it makes no difference whether the actual cache behavior is write-through (as configured) or write back.

    Kind regards
    Marcus
Children
No data