Login

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

ARM Community: does TTBR RGN,S bits need to match those in page table entry ? - ARM Community

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

does TTBR RGN,S bits need to match those in page table entry ? Rate Topic: -----

#1 User is offline   lsjk 

  • Member
  • Pip
  • Group: Members
  • Posts: 3
  • Joined: 06-April 12

Posted 07 April 2012 - 07:58 AM

Hi experts,

On cortex-a9, does TTBR RGN,S bits need to match those in page table entry ?
For example, if I set TTBR RGN bits = WBWA (inner and outter write back write allocate) to let
TLB walk happen in cache, and set the memory that contains page tables
to TEX,C,B = 0,0,0 (strongly ordered). Will this work ? Or the memory contains page tables must also be set to WBWA ? Thanks.
0

#2 User is offline   ttfn 

  • Super Contributor
  • PipPipPipPip
  • Group: Members
  • Posts: 576
  • Joined: 29-September 06

Posted 07 April 2012 - 12:55 PM

Yes and no.
Those settings are used when the processor does a table walk. If you the settings don't match the appropriate table entries, there is a risk of coherency problems.
Typically you either match the settings, or set RGN bits to uncached and do a cache clean after table modifications.
1

#3 User is offline   lsjk 

  • Member
  • Pip
  • Group: Members
  • Posts: 3
  • Joined: 06-April 12

Posted 09 April 2012 - 02:11 AM

瀏覽文章引用框(ttfn @ 07 April 2012 - 12:55 PM)

Yes and no.
Those settings are used when the processor does a table walk. If you the settings don't match the appropriate table entries, there is a risk of coherency problems.
Typically you either match the settings, or set RGN bits to uncached and do a cache clean after table modifications.


I understand. But consider this: what if I configure ttbr to inner and outter WBWA, but page table to strongly-order, will this work ? For what I understand, the memory that contains page table will never be brought into cache because I put page tables into strongly ordered memory, and when tlb walk happens, it will cause a cache miss and fetch data from external memory. So in this case the tlb walk and CPU also see consistent data, only this time the memory access will be slower ? I am asking because I see a little bit faster tlb walk than other configurations which is weird because SO memory is supposed to be very slow.
1

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic