Re: [PATCH 3/5] x86-64, docs, mm: Add vsyscall range to virtual addressspace layout

[Andy Lutomirski]

On 03/04/2013 12:16 PM, Borislav Petkov wrote:
> Add the end of the virtual address space to its layout documentation.
> 
> Signed-off-by: Borislav Petkov <bp@xxxxxxxxx>
> ---
>  Documentation/x86/x86_64/mm.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/x86/x86_64/mm.txt b/Documentation/x86/x86_64/mm.txt
> index d6498e3cd713..881582f75c9c 100644
> --- a/Documentation/x86/x86_64/mm.txt
> +++ b/Documentation/x86/x86_64/mm.txt
> @@ -13,7 +13,9 @@ ffffe90000000000 - ffffe9ffffffffff (=40 bits) hole
>  ffffea0000000000 - ffffeaffffffffff (=40 bits) virtual memory map (1TB)
>  ... unused hole ...
>  ffffffff80000000 - ffffffffa0000000 (=512 MB)  kernel text mapping, from phys 0
> -ffffffffa0000000 - fffffffffff00000 (=1536 MB) module mapping space
> +ffffffffa0000000 - ffffffffff5fffff (=1525 MB) module mapping space
> +ffffffffff600000 - ffffffffffdfffff (=8 MB) vsyscalls
> +ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
>  
>  The direct mapping covers all memory in the system up to the highest
>  memory address (this means in some cases it can also include PCI memory
> 

vsyscalls are only 4k.  Am I missing something obvious her?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/