From: tip-bot for Borislav Petkov <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
tglx@linutronix.de, hpa@linux.intel.com, bp@alien8.de
Subject: [tip:x86/cleanups] x86-64, docs, mm: Add vsyscall range to virtual address space layout
Date: Tue, 2 Apr 2013 17:19:35 -0700 [thread overview]
Message-ID: <tip-aca91bfc67fe356544eb1cfc483c09b27ce49fa9@git.kernel.org> (raw)
In-Reply-To: <1362428180-8865-4-git-send-email-bp@alien8.de>
Commit-ID: aca91bfc67fe356544eb1cfc483c09b27ce49fa9
Gitweb: http://git.kernel.org/tip/aca91bfc67fe356544eb1cfc483c09b27ce49fa9
Author: Borislav Petkov <bp@alien8.de>
AuthorDate: Mon, 4 Mar 2013 21:16:18 +0100
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Tue, 2 Apr 2013 16:03:31 -0700
x86-64, docs, mm: Add vsyscall range to virtual address space layout
Add the end of the virtual address space to its layout documentation.
Signed-off-by: Borislav Petkov <bp@alien8.de>
Link: http://lkml.kernel.org/r/1362428180-8865-4-git-send-email-bp@alien8.de
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
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 d6498e3..881582f 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
next prev parent reply other threads:[~2013-04-03 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 20:16 [PATCH 0/5] x86: Misc fixlets Borislav Petkov
2013-03-04 20:16 ` [PATCH 1/5] x86, smpboot: Remove unused variable Borislav Petkov
2013-03-06 0:24 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 2/5] x86: Drop KERNEL_IMAGE_START Borislav Petkov
2013-04-03 0:18 ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 3/5] x86-64, docs, mm: Add vsyscall range to virtual address space layout Borislav Petkov
2013-03-04 21:45 ` Andy Lutomirski
2013-03-04 21:56 ` Borislav Petkov
2013-04-03 0:19 ` tip-bot for Borislav Petkov [this message]
2013-03-04 20:16 ` [PATCH 4/5] x86, msr: Unify variable names Borislav Petkov
2013-04-03 0:20 ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 5/5] x86, quirks: Shut-up a long-standing gcc warning Borislav Petkov
2013-04-03 0:21 ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-aca91bfc67fe356544eb1cfc483c09b27ce49fa9@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@alien8.de \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome