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

Control MMU for TrustZone

Note: This was originally posted on 20th July 2011 at http://forums.arm.com

Dear all,
I am a new bie about TrustZone. I arm learning the effect of TrustZone to MMU. I have some problems about the mechanism to manage secure/non-secure region by MMU.
Please help me to understand about them.
My dubious point described as below:
   When translation virtual address to physical address, system will use TLB table. I know that, when have a miss occur on TLB, it will find physical page from page table.
From table index of virtual address and table base address, will have first-level descriptor, the first-level descriptor will be input for page table to get physical page table from page table
then fill it to TLB table.
If page table miss, it will find physical page form external memory (RAM) and fill it to page table with it's attribute.
So when cpu stay in secure world, and access to secure physical memory
     How to know the address that cpu access include secure physical memory region or no-secure physical memory region?
     How to partition the physical memory into secure and non-secure regions?
and if know secure attribute of secure region then
     How to fill secure attribute to page table?
Please help me.
Thank you very much,

Parents

Martin Weidmann over 12 years ago

Note: This was originally posted on 25th July 2011 at http://forums.arm.com

You said:

" If processor don't know whether secure page or non-secure page, the implementation TZASC, TZMA not meaning. How to fill the status of NS bit for L1 descriptor by hardware?"

The processor does not know - that is your job!

When you set up the page tables, it is up to you to correctly set/clear the NS bit of each entry. This involves you knowing what the layout of memory is in your system, and how you have configured any controllers (e.g. TZPV or TZASC). Typically this information will come from the data sheet for the part.

As already discussed, the processor will always use secure accesses to for a table walk while in the Secure world. So again it is down to you to put the page tables in appropriate memory.
Cancel
Vote up 0 Vote down

Cancel

Reply

Martin Weidmann over 12 years ago

Note: This was originally posted on 25th July 2011 at http://forums.arm.com

You said:

" If processor don't know whether secure page or non-secure page, the implementation TZASC, TZMA not meaning. How to fill the status of NS bit for L1 descriptor by hardware?"

The processor does not know - that is your job!

When you set up the page tables, it is up to you to correctly set/clear the NS bit of each entry. This involves you knowing what the layout of memory is in your system, and how you have configured any controllers (e.g. TZPV or TZASC). Typically this information will come from the data sheet for the part.

As already discussed, the processor will always use secure accesses to for a table walk while in the Secure world. So again it is down to you to put the page tables in appropriate memory.
Cancel
Vote up 0 Vote down

Cancel

Children

No data