lkml.org 
[lkml]   [2014]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRE: [PATCH v3] arm: ioremap: Fix static vm area boundary check.
On Mon, 19 May 2014, Li.Xiubo@freescale.com wrote:

> > > For each vmalloc area, there is one guard page at the end of it.
> > > so the vm->size = PAGE_ALIGN(offset + request size) + guard page size.
> >
> > Nope. There is no guard page for statically created vmalloc areas.
> >
>
> Yes, you are right, I'm thinking why the static area has no guard page?

The virtual addresses being used are provided by the static mapping
descriptions themselves. Sometimes those mappings are large and
contiguous, covering multiple peripherals at once with a single TLB,
etc. There is simply no room for a guard page, or no guard page at all
between different areas covered by a single section mapping (1MB worth
of mapping from a single page table entry).

All this to say that trying to enforce a guard page in those cases is
likely to throw away all the performance advantage and conplexify
things.


Nicolas


\
 
 \ /
  Last update: 2014-05-20 05:41    [W:0.101 / U:0.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site