lkml.org 
[lkml]   [2013]   [Mar]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 3/5] x86-64, docs, mm: Add vsyscall range to virtual address space layout
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@alien8.de>
> ---
> 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?


\
 
 \ /
  Last update: 2013-03-04 23:21    [W:2.799 / U:0.440 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site