From: Joseph Cihula <joseph.cihula@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: shane.wang@intel.com, gang.wei@intel.com, arjan@linux.intel.com,
asit.k.mallick@intel.com, jun.nakajima@intel.com,
chrisw@sous-sol.org, jbeulich@novell.com, mingo@elte.hu,
tytso@mit.edu, joseph.cihula@intel.com
Subject: Re: [RFC][PATCH 1/3] TXT: ACPI AddressRangeUnusuable support
Date: Tue, 07 Oct 2008 16:40:02 -0700 [thread overview]
Message-ID: <48EBF352.6080601@linux.intel.com> (raw)
In-Reply-To: <48EBE96A.6080700@linux.intel.com>
(still managed to lose the tabs--let's try one more time ;-( )
(re-posted with apologies for formatting and email addresses)
Commit message (w/ patch), copied below:
Add support for the E820_UNUSABLE memory type, which is defined in Revision 3.0b (Oct. 10, 2006) of the ACPI Specification on p. 394 Table
14-1:
AddressRangeUnusuable This range of address contains memory in which
errors have been detected. This range must not be used by the OSPM.
Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
Signed-off-by: Shane Wang <shane.wang@intel.com>
Signed-off-by: Gang Wei <gang.wei@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/x86/kernel/e820.c | 4 ++++
include/asm-x86/e820.h | 1 +
2 files changed, 5 insertions(+)
diff -puN arch/x86/kernel/e820.c~acpi-add-support-for-addressrangeunusuable-acpi-memory-type arch/x86/kernel/e820.c
--- a/arch/x86/kernel/e820.c~acpi-add-support-for-addressrangeunusuable-acpi-memory-type
+++ a/arch/x86/kernel/e820.c
@@ -148,6 +148,9 @@ void __init e820_print_map(char *who)
case E820_NVS:
printk(KERN_CONT "(ACPI NVS)\n");
break;
+ case E820_UNUSABLE:
+ printk("(unusable)\n");
+ break;
default:
printk(KERN_CONT "type %u\n", e820.map[i].type);
break;
@@ -1260,6 +1263,7 @@ static inline const char *e820_type_to_s
case E820_RAM: return "System RAM";
case E820_ACPI: return "ACPI Tables";
case E820_NVS: return "ACPI Non-volatile Storage";
+ case E820_UNUSABLE: return "Unusable memory";
default: return "reserved";
}
}
diff -puN include/asm-x86/e820.h~acpi-add-support-for-addressrangeunusuable-acpi-memory-type include/asm-x86/e820.h
--- a/include/asm-x86/e820.h~acpi-add-support-for-addressrangeunusuable-acpi-memory-type
+++ a/include/asm-x86/e820.h
@@ -43,6 +43,7 @@
#define E820_RESERVED 2
#define E820_ACPI 3
#define E820_NVS 4
+#define E820_UNUSABLE 5
/* reserved RAM used by kernel itself */
#define E820_RESERVED_KERN 128
next prev parent reply other threads:[~2008-10-07 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 22:57 [RFC][PATCH 1/3] TXT: ACPI AddressRangeUnusuable support Joseph Cihula
2008-10-07 23:40 ` Joseph Cihula [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 20:34 Cihula, Joseph
2008-10-08 0:54 ` Andi Kleen
2008-10-08 4:32 ` Cihula, Joseph
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=48EBF352.6080601@linux.intel.com \
--to=joseph.cihula@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@sous-sol.org \
--cc=gang.wei@intel.com \
--cc=jbeulich@novell.com \
--cc=joseph.cihula@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shane.wang@intel.com \
--cc=tytso@mit.edu \
/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