From: Christoph Lameter <clameter@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: travis@sgi.com, linux-kernel@vger.kernel.org
Subject: [patch 2/4] x86: e820 unification: Extract shared comments
Date: Mon, 05 May 2008 12:02:15 -0700 [thread overview]
Message-ID: <20080505190242.254641759@sgi.com> (raw)
In-Reply-To: 20080505190213.714827651@sgi.com
[-- Attachment #1: e820_comments --]
[-- Type: text/plain, Size: 2114 bytes --]
The comments are basically the same. Take the 64 bit version as the common
comments.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
---
include/asm-x86/e820.h | 26 +++++++-------------------
1 file changed, 7 insertions(+), 19 deletions(-)
Index: linux-next/include/asm-x86/e820.h
===================================================================
--- linux-next.orig/include/asm-x86/e820.h 2008-05-04 23:03:30.799851792 -0700
+++ linux-next/include/asm-x86/e820.h 2008-05-04 23:04:37.939859869 -0700
@@ -29,20 +29,20 @@ struct e820map {
#define BIOS_END 0x00100000
#ifdef __KERNEL__
-#ifdef CONFIG_X86_32
+
/*
* structures and definitions for the int 15, ax=e820 memory map
* scheme.
*
- * In a nutshell, arch/i386/boot/setup.S populates a scratch table
- * in the empty_zero_block that contains a list of usable address/size
- * duples. In arch/i386/kernel/setup.c, this information is
- * transferred into the e820map, and in arch/i386/mm/init.c, that
- * new information is used to mark pages reserved or not.
- *
+ * In a nutshell, setup.S populates a scratch table in the
+ * empty_zero_block that contains a list of usable address/size
+ * duples. setup.c, this information is transferred into the e820map,
+ * and in init.c/numa.c, that new information is used to mark pages
+ * reserved or not.
*/
#include <linux/ioport.h>
+#ifdef CONFIG_X86_32
#define HIGH_MEMORY (1024*1024)
#ifndef __ASSEMBLY__
@@ -79,18 +79,6 @@ static inline void e820_mark_nosave_regi
#endif/*!__ASSEMBLY__*/
#else /* X86_32 */
-/*
- * structures and definitions for the int 15, ax=e820 memory map
- * scheme.
- *
- * In a nutshell, setup.S populates a scratch table in the
- * empty_zero_block that contains a list of usable address/size
- * duples. setup.c, this information is transferred into the e820map,
- * and in init.c/numa.c, that new information is used to mark pages
- * reserved or not.
- */
-#include <linux/ioport.h>
-
#ifndef __ASSEMBLY__
extern unsigned long find_e820_area(unsigned long start, unsigned long end,
unsigned long size, unsigned long align);
--
next prev parent reply other threads:[~2008-05-05 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 19:02 [patch 0/4] [PATCH] x86: Merge e820_32/64 Christoph Lameter
2008-05-05 19:02 ` [patch 1/4] x86: e820.h unification Christoph Lameter
2008-05-05 19:02 ` Christoph Lameter [this message]
2008-05-05 19:02 ` [patch 3/4] x86: e820 unification: Common #ifdef __ASSEMBLY Christoph Lameter
2008-05-05 19:02 ` [patch 4/4] x86: e820 unification: Extract common functions Christoph Lameter
2008-05-06 11:35 ` Adrian Bunk
2008-05-06 12:32 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-05-06 19:33 [patch 0/4] [PATCH] x86: Merge e820_32/64 V2 Christoph Lameter
2008-05-06 19:33 ` [patch 2/4] x86: e820 unification: Extract shared comments Christoph Lameter
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=20080505190242.254641759@sgi.com \
--to=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.com \
/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