From: Maneesh Soni <maneesh@in.ibm.com>
To: kexec@lists.infradead.org
Subject: Re: ELF64 header on i386
Date: Tue, 3 Jul 2007 10:42:28 +0530 [thread overview]
Message-ID: <20070703051228.GA8394@in.ibm.com> (raw)
In-Reply-To: <20070702131541.GA6084@suse.de>
On Mon, Jul 02, 2007 at 03:15:41PM +0200, Bernhard Walle wrote:
> Hello,
>
> why creates kexec-tools ELF64 headers per default on i386? Wouldn't it
> make more sense to look if a physical address exceeds the 32-bit limit
> and then switch to ELF64 automatically if the user doesn't have
> specified an option?
>
I am aware of one issue, that gdb on i386 is not able to analyse ELF64
formatted kdump though "crash" can.
Thanks
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM India Systems and Technology Lab,
Bangalore, India
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-07-03 5:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 13:15 ELF64 header on i386 Bernhard Walle
2007-07-03 5:12 ` Maneesh Soni [this message]
2007-07-03 16:12 ` [PATCH] Determine ELF32/ELF64 automatically " Bernhard Walle
2007-07-10 5:52 ` Vivek Goyal
2007-07-10 8:23 ` Bernhard Walle
2007-07-27 5:12 ` 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=20070703051228.GA8394@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=kexec@lists.infradead.org \
/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