From: Jay Lan <jlan@sgi.com>
To: linux-ia64@vger.kernel.org
Cc: Jack Steiner <steiner@sgi.com>, kexec@lists.infradead.org
Subject: [PATCH]IA64: assign a distinguishable label to uncached memory in
Date: Thu, 11 Sep 2008 23:00:08 +0000 [thread overview]
Message-ID: <48C9A2F8.3060308@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Currently a memory segment in memory map with attribute of EFI_MEMORY_UC
is denoted as "System RAM" in /proc/iomem, while memory of attribute
(EFI_MEMORY_WB|EFI_MEMORY_UC) is also labeled the same.
The kexec utility then includes uncached memory as part of vmcore. The
kdump kernel MCA'ed when it tries to save the vmcore to a disk. A normal
"cached" access may cause MCAs.
This patch would label memory with attribute of EFI_MEMORY_UC only as
"Uncached RAM" so that kexec would know not to include it in the vmcore.
I will submit a separate kexec-tools patch to the kexec list.
Signed-off-by: Jay Lan <jlan@sgi.com>
[-- Attachment #2: UC-mem --]
[-- Type: text/plain, Size: 647 bytes --]
---
arch/ia64/kernel/efi.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: linux/arch/ia64/kernel/efi.c
===================================================================
--- linux.orig/arch/ia64/kernel/efi.c
+++ linux/arch/ia64/kernel/efi.c
@@ -1232,9 +1232,10 @@ efi_initialize_iomem_resources(struct re
if (md->attribute & EFI_MEMORY_WP) {
name = "System ROM";
flags |= IORESOURCE_READONLY;
- } else {
- name = "System RAM";
- }
+ } else if (md->attribute == EFI_MEMORY_UC)
+ name = "Uncached RAM";
+ else
+ name = "System RAM";
break;
case EFI_ACPI_MEMORY_NVS:
next reply other threads:[~2008-09-11 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 23:00 Jay Lan [this message]
2008-09-12 7:55 ` [PATCH]IA64: assign a distinguishable label to uncached memory Bernhard Walle
2008-09-12 7:58 ` Bernhard Walle
2008-09-12 13:57 ` Jay Lan
2008-09-15 5:10 ` Simon Horman
2008-09-15 17:08 ` Jay Lan
2008-09-15 23:49 ` Simon Horman
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=48C9A2F8.3060308@sgi.com \
--to=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=steiner@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