All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Ian Campbell <Ian.Campbell@xensource.com>,
	Horms <horms@verge.net.au>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps
Date: Fri, 16 Mar 2007 17:08:01 +0530	[thread overview]
Message-ID: <20070316113801.GC5642@in.ibm.com> (raw)
In-Reply-To: <aec7e5c30703160305p5d91af41h147e3a6c2687bcd9@mail.gmail.com>

On Fri, Mar 16, 2007 at 07:05:30PM +0900, Magnus Damm wrote:
> On 3/16/07, Vivek Goyal <vgoyal@in.ibm.com> wrote:
> >Got a question. When running 32bit dom0 on 64bit hypervisor, which
> >kexec-tools elf loader will kick in? 32bit or 64bit? Looks like in this
> >case 64bit one. But shouldn't it be 32bit as 32bit OS is running and we
> >must be using the kexec-tools binary compiled for 32bit OS? And if 32bit
> >loader kicks in we will not be passing any acpi parameters.
> 
> There is no check to see if the hypervisor is 32 or 64 bits present
> today. So the 32-bit version of kexec-tools will support loading
> images like any other 32-bit kexec-tools.
> 

If that is the case then in prepared elf headers, machine type should
be EM_386 or similar and not EM_X86_64 and Ian shouldn't have run into
the problem at all with vmcore. Am I missing something?

Thanks
Vivek

  reply	other threads:[~2007-03-16 11:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 17:00 [PATCH 1/1] Allow i386 crash kernels to handle x86_64 dumps 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
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 [this message]
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=20070316113801.GC5642@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=Ian.Campbell@xensource.com \
    --cc=fastboot@lists.osdl.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.