public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	tglx@linutronix.de, hpa@zytor.com
Subject: [PATCH 2/2] x86_64: use PAGE_OFFSET in dump_pagetables
Date: Thu,  1 May 2008 11:58:19 +0200	[thread overview]
Message-ID: <1209635899-23018-2-git-send-email-jirislaby@gmail.com> (raw)
In-Reply-To: <1209635899-23018-1-git-send-email-jirislaby@gmail.com>

Use PAGE_OFFSET macro instead of using 0xffff810000000000UL directly.

Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: tglx@linutronix.de
Cc: mingo@redhat.com
Cc: hpa@zytor.com
---
 arch/x86/mm/dump_pagetables.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/mm/dump_pagetables.c b/arch/x86/mm/dump_pagetables.c
index 6791b83..6f8e3fe 100644
--- a/arch/x86/mm/dump_pagetables.c
+++ b/arch/x86/mm/dump_pagetables.c
@@ -42,7 +42,7 @@ static struct addr_marker address_markers[] = {
 	{ 0, "User Space" },
 #ifdef CONFIG_X86_64
 	{ 0x8000000000000000UL, "Kernel Space" },
-	{ 0xffff810000000000UL, "Low Kernel Mapping" },
+	{ PAGE_OFFSET,		"Low Kernel Mapping" },
 	{ VMALLOC_START,        "vmalloc() Area" },
 	{ VMEMMAP_START,        "Vmemmap" },
 	{ __START_KERNEL_map,   "High Kernel Mapping" },
-- 
1.5.4.5


  reply	other threads:[~2008-05-01  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01  9:58 [PATCH 1/2] x86_64: fix mm.txt documentation Jiri Slaby
2008-05-01  9:58 ` Jiri Slaby [this message]
2008-05-02  7:33   ` [PATCH 2/2] x86_64: use PAGE_OFFSET in dump_pagetables Ingo Molnar
2008-05-02  7:22 ` [PATCH 1/2] x86_64: fix mm.txt documentation Ingo Molnar
2008-05-02  7:57   ` Jiri Slaby
2008-05-02  8:38   ` Andi Kleen
2008-05-02  8:47     ` Jiri Slaby
2008-05-02  8:00 ` Andi Kleen
2008-05-02  7:55   ` Jiri Slaby

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=1209635899-23018-2-git-send-email-jirislaby@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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