From: Ian Campbell <Ian.Campbell@XenSource.com>
To: vgoyal@in.ibm.com, hbabu@us.ibm.com
Cc: fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
Horms <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps
Date: Wed, 14 Mar 2007 17:00:09 +0000 [thread overview]
Message-ID: <1173891609.8591.41.camel@localhost.localdomain> (raw)
The specific case I am encountering is kdump under Xen with a 64 bit
hypervisor and 32 bit kernel/userspace. The dump created is a 64 bit due
to the hypervisor but the dump kernel is 32 bit to match the domain 0
kernel.
It's possibly less likely to be useful in a purely native scenario but I
see no reason to disallow it.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
--- pristine-linux-2.6.18/include/asm-i386/elf.h 2006-09-20 04:42:06.000000000 +0100
+++ linux-2.6.18-xen/include/asm-i386/elf.h 2007-03-14 16:42:30.000000000 +0000
@@ -36,7 +36,7 @@
* This is used to ensure we don't load something for the wrong architecture.
*/
#define elf_check_arch(x) \
- (((x)->e_machine == EM_386) || ((x)->e_machine == EM_486))
+ (((x)->e_machine == EM_386) || ((x)->e_machine == EM_486) || ((x)->e_machine == EM_X86_64))
/*
* These are used to set parameters in the core dumps.
next reply other threads:[~2007-03-14 17:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 17:00 Ian Campbell [this message]
2007-03-15 1:46 ` [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps Horms
2007-03-15 4:55 ` Vivek Goyal
2007-03-15 5:07 ` Horms
2007-03-15 5:47 ` Vivek Goyal
2007-03-15 8:00 ` Horms
2007-03-15 12:22 ` Ian Campbell
2007-03-15 13:26 ` Vivek Goyal
2007-03-15 13:42 ` Ian Campbell
2007-03-15 23:46 ` Horms
2007-03-16 2:27 ` Vivek Goyal
2007-03-15 23:48 ` Horms
2007-03-16 2:40 ` [Fastboot] " Magnus Damm
2007-03-16 3:22 ` Vivek Goyal
2007-03-16 7:10 ` Horms
2007-03-16 7:50 ` Magnus Damm
2007-03-16 7:28 ` Ian Campbell
2007-03-16 7:59 ` Magnus Damm
2007-03-16 8:50 ` Ian Campbell
2007-03-16 9:20 ` Magnus Damm
2007-03-16 9:35 ` Vivek Goyal
2007-03-16 10:05 ` Magnus Damm
2007-03-16 11:38 ` Vivek Goyal
2007-03-16 11:40 ` Ian Campbell
2007-03-16 12:25 ` Vivek Goyal
2007-03-16 12:31 ` Vivek Goyal
2007-03-16 9:26 ` Vivek Goyal
2007-03-16 2:42 ` Vivek Goyal
2007-03-16 7:31 ` Ian Campbell
2007-03-16 7:17 ` Ian Campbell
2007-03-16 7:30 ` Horms
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=1173891609.8591.41.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=fastboot@lists.osdl.org \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=vgoyal@in.ibm.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