From: "Magnus Damm" <magnus.damm@gmail.com>
To: Horms <horms@verge.net.au>
Cc: "Vivek Goyal" <vgoyal@in.ibm.com>,
fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
"Ian Campbell" <Ian.Campbell@xensource.com>
Subject: Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps
Date: Fri, 16 Mar 2007 16:50:46 +0900 [thread overview]
Message-ID: <aec7e5c30703160050w65df9cfaoafd469d1a37bdc4e@mail.gmail.com> (raw)
In-Reply-To: <20070316071031.GB6689@verge.net.au>
On 3/16/07, Horms <horms@verge.net.au> wrote:
> On Fri, Mar 16, 2007 at 08:52:30AM +0530, Vivek Goyal wrote:
> > So it will now be left to the user. If he tries to kexec to a 64bit kernel
> > on a machine not supporting 32bit extensions, then kexec will not give
> > any advance warning.
>
> I feel comfortable with that. Well for now anyway.
> But I think that Magnus has other ideas.
I don't mind switching back and forth between 32-bit and 64-bit for
plain kexec, especially if we can validate that the kernel we load
will use an instruction set that is supported. But for kdump,
switching between 32-bit and 64-bit kernels is just another new
dimension in the already too complex kdump matrix IMO.
I think more focus should be put on fixing up bugs in kexec-tools than
adding new features.
/ magnus
next prev parent reply other threads:[~2007-03-16 7:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 17:00 Ian Campbell
2007-03-15 1:46 ` 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 [this message]
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=aec7e5c30703160050w65df9cfaoafd469d1a37bdc4e@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=Ian.Campbell@xensource.com \
--cc=fastboot@lists.osdl.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®