1. 09 11月, 2012 1 次提交
    • W
      ARM: mm: introduce L_PTE_VALID for page table entries · dbf62d50
      Will Deacon 提交于
      For long-descriptor translation table formats, the ARMv7 architecture
      defines the last two bits of the second- and third-level descriptors to
      be:
      
      	x0b	- Invalid
      	01b	- Block (second-level), Reserved (third-level)
      	11b	- Table (second-level), Page (third-level)
      
      This allows us to define L_PTE_PRESENT as (3 << 0) and use this value to
      create ptes directly. However, when determining whether a given pte
      value is present in the low-level page table accessors, we only need to
      check the least significant bit of the descriptor, allowing us to write
      faulting, present entries which are required for PROT_NONE mappings.
      
      This patch introduces L_PTE_VALID, which can be used to test whether a
      pte should fault, and updates the low-level page table accessors
      accordingly.
      Signed-off-by: NWill Deacon <will.deacon@arm.com>
      dbf62d50
  2. 03 10月, 2012 1 次提交
  3. 11 8月, 2012 2 次提交
  4. 03 1月, 2012 1 次提交
  5. 08 12月, 2011 3 次提交
  6. 06 12月, 2011 2 次提交
  7. 27 11月, 2011 2 次提交
    • N
      ARM: move VMALLOC_END down temporarily for shmobile · 0af362f8
      Nicolas Pitre 提交于
      THIS IS A TEMPORARY HACK.  The purpose of this is _only_ to avoid a
      regression on an existing machine while a better fix is implemented.
      
      On shmobile the consistent DMA memory area was set to 158MB in commit
      28f0721a with no explanation.  The documented size for this area should
      vary between 2MB and 14MB, and none of the other ARM targets exceed that.
      
      The included #warning is therefore meant to be noisy on purpose to get
      shmobile maintainers attention and this commit reverted once this
      consistent DMA size conflict is resolved.
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      Cc: Magnus Damm <damm@opensource.se>
      Cc: Paul Mundt <lethal@linux-sh.org>
      0af362f8
    • N
      ARM: move iotable mappings within the vmalloc region · 0536bdf3
      Nicolas Pitre 提交于
      In order to remove the build time variation between different SOCs with
      regards to VMALLOC_END, the iotable mappings are now allocated inside
      the vmalloc region.  This allows for VMALLOC_END to be identical across
      all machines.
      
      The value for VMALLOC_END is now set to 0xff000000 which is right where
      the consistent DMA area starts.
      
      To accommodate all static mappings on machines with possible highmem usage,
      the default vmalloc area size is changed to 240 MB so that VMALLOC_START
      is no higher than 0xf0000000 by default.
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      Tested-by: NStephen Warren <swarren@nvidia.com>
      Tested-by: NKevin Hilman <khilman@ti.com>
      Tested-by: NJamie Iles <jamie@jamieiles.com>
      0536bdf3
  8. 06 10月, 2011 2 次提交
  9. 23 9月, 2011 1 次提交
  10. 22 2月, 2011 1 次提交
  11. 15 2月, 2011 1 次提交
  12. 22 12月, 2010 5 次提交
  13. 27 11月, 2010 6 次提交
  14. 21 11月, 2010 1 次提交
  15. 27 10月, 2010 1 次提交
  16. 19 9月, 2010 2 次提交
  17. 17 5月, 2010 1 次提交
  18. 25 11月, 2009 1 次提交
  19. 18 8月, 2009 1 次提交
  20. 11 7月, 2009 2 次提交
  21. 05 7月, 2009 2 次提交
  22. 26 4月, 2009 1 次提交