Control MMU for TrustZone Control MMU for TrustZone
Posted 20 July 2011 - 12:14 PM
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,
Posted 20 July 2011 - 05:22 PM
The NS bit is ignored if the processor is running in the "non-secure" world, the hardware forces NS=1 in this case.
Posted 21 July 2011 - 10:10 AM
- Which world the TLB entry belongs to
- Whether the memory being described should be accessed using secure or non-secure accesses
The second one then... The Normal world can only generate non-secure memory accesses. So when a Normal world TLB entry is used, the processor will just assume that any accesses with be marked non-secure.
The SEcure world can generate secure or non-secure accesses. What will be used for given address range is controlled by the NS bit in the descriptors. For Secure world TLB entries, the value of this bit is stored along side teh translation and other attributes.
Posted 22 July 2011 - 09:00 AM
I still some dubious point.
I know that each line on TLB has 2 attribute NS and NSTID. They will specify the descriptor and physical page on each line of TLB is secure or non-secure.
But when has a miss TLB, it must find corresponding physical page at page table then fill it to TLB, so
How to specify this physical page is secure or non-secure?
How will TLB update NS and NSTID for this entry?
Can you indicate them for me?
Posted 22 July 2011 - 10:19 AM
When the secure world makes a table walk that walk is always made as secure. When the normal world makes a table walk it is always made as non-secure.
> How will TLB update NS and NSTID for this entry?
NSTID = currently world of the processor.
NS = the NS bit from the L1 descriptor if in secure-world, one otherwise.
EDIT: corrected NS-bit description above.
This post has been edited by isogen74: 25 July 2011 - 09:21 AM
Posted 22 July 2011 - 11:18 AM
I think when the secure world makes a table walk that walk can be secure or non-secure, it depends on the physical page on page table mapped secure or non-secure.
I know that for some TrustZone systems implemented TZASC, TZMA to partition secure and non-secure memory regions. So when have a miss on page table,
it must find this page from main memory (DRAM) and determine whether it is secure or non-secure memory region (by check signal on TZASC for the memory region that it access to)
then fill it to page table with the status of this page on memory region.
My understand is correct or incorrect? Can you explain for me?
> NSTID = currently world of the processor.
> NS = the NS bit from the L1 descriptor if in secure-world, zero otherwise.
Will NS bit from the L1 descriptor specify by attribute on page table?
The mean that when find physical page from page table then NS bit on descriptor will be updated by an secure attribute on page table but I don't know the attribute.
It my understand correct. Can you indicate what is the secure attribute on page table?
Posted 22 July 2011 - 03:35 PM
When in the secure world, the walk of the l1 table will _always_ be done using secure accesses. Why? Well, because the processor only has a pointer to the L1 tables (TTBR0/1). It is the tables which define whether secure or non-secure accesses will be used for a particular address range. Therefore until it reads the table it has no way of knowing whether to use secure or non-secure accesses. So, while in the Secure world, the processor will always use secure accesses for the table walk.
Does this matter?
Well, first why would you want the page tables for the Secure world in memory accessible by the Normal world? This seems like a bit of flaw in your software!
Also, the processor does not know whether the target address accepts secure or non-secure (or both!) accesses. The target memory doesn't support the generated access type it will return an error, and the processor will take an abort. There is no auto-sensing system for the processor to discover the kind of access to use.
Posted 25 July 2011 - 01:45 AM
Yes, in the secure world , the walk always use secure accesses
>> Does this matter?
>> Well, first why would you want the page tables for the Secure world in memory accessible by the
>>Normal world? This seems like a bit of flaw in your software!
I know Normal world don't access to page table for secure world, that at here I want the page table for Normal world in memory accessible by the Secure world
>> Also, the processor does not know whether the target address accepts secure or non-secure (or both!)
>>accesses. The target memory doesn't support the generated access type it will return an error, and the
>>processor will take an abort. There is no auto-sensing system for the processor to discover the kind of access
At here, I want to talk about the TrustZone hardware architecture. I have a point that is not clear is
- Processor makes a table walk, and the physical page on the page table found
- 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?
I think when have a miss on page table, it will find the page on RAM and when it found the page on RAM, It know the page is secure or non-secure page by TZASC, TZMA
because TZASC, TZMA divided the memory on RAM into secure and non-secure regions.
How do you think?
This post has been edited by Hero132: 25 July 2011 - 02:28 AM
Posted 25 July 2011 - 08:33 AM
" 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.