All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: kexec@lists.infradead.org
Subject: Re: [PATCH 0/8] kexec build system updates, to allow cross-kexec()ing
Date: Wed, 19 Dec 2007 14:37:34 +0900	[thread overview]
Message-ID: <200712191437.35644.jk@ozlabs.org> (raw)
In-Reply-To: <20071218232558.GA14092@redhat.com>

(resend to kexec list)

Hi Vivek,

> I got a stupid question.
>
> - What's the advantage of building a 32bit binary for powerpc64 bit
>   platforms?

So you don't need to have 64-bit libc and libz present. It's often the 
case that you have an entire 32-bit userspace environment, but still 
require 64-bit libraries just for the kexec program.

>   IOW, why do you need to build 32bit purgatory?

We build the purgatory for the $target architecture, that's all. My 
setup involves:

 build: powerpc-linux-gnu
 host: powerpc-linux-uclibc
 target: powerpc64-linux-uclibc

So I'm aiming for a 64-bit purgatory here, we generally tend to boot 
64-bit kernels on powerpc64 machines.

>   Can't we launch 32bit kernel from 64bit purgatory?

I assume so, but you wouldn't be able to do this on 32-bit machines, of 
course. I haven't been trying the case where the purgatory arch != 
kernel arch.

> > This allows us to kexec a powerpc64 kernel from a powerpc
> > userspace. x86{,_64} users might find this handy too, but I don't
> > have hardware to test.
>
> I think x86 it already happens. I think I can launch 64bit kernel
> from a 32bit kexec.

OK, this change should make this possible for all arches, just by 
specifying --host and --target - are you able to make sure that you can 
build a kexec where host=i386-linux and target=x86_64-linux ?

Cheers,


Jeremy


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2007-12-19  5:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18  8:47 [PATCH 0/8] kexec build system updates, to allow cross-kexec()ing Jeremy Kerr
2007-12-18  8:47 ` [PATCH 1/8] Enable building a 32 bit binary for ppc64 platforms Jeremy Kerr
2007-12-19  6:02   ` Geoff Levand
2007-12-18  8:47 ` [PATCH 4/8] Use config.h for defines Jeremy Kerr
2007-12-18  8:47 ` [PATCH 7/8] removed partially duplicated system headers Jeremy Kerr
2007-12-18  8:47 ` [PATCH 8/8] Don't assume we can re-make Makefile Jeremy Kerr
2007-12-18  8:47 ` [PATCH 3/8] Consolidate BOOTLOADER defines Jeremy Kerr
2007-12-18  8:47 ` [PATCH 2/8] Use --target for target architecture specification Jeremy Kerr
2007-12-18  8:47 ` [PATCH 6/8] Build system simplification/standardisation Jeremy Kerr
2007-12-18  8:47 ` [PATCH 5/8] Add gamecube to config.h defines Jeremy Kerr
2007-12-18 23:25 ` [PATCH 0/8] kexec build system updates, to allow cross-kexec()ing Vivek Goyal
2007-12-19  5:37   ` Jeremy Kerr [this message]
2007-12-19 14:38   ` Lombard, David N
2007-12-19 14:45     ` Vivek Goyal
2007-12-19  6:04 ` 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=200712191437.35644.jk@ozlabs.org \
    --to=jk@ozlabs.org \
    --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 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.