From: Mohan Kumar M <mohan@in.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support
Date: Mon, 18 Aug 2008 22:49:25 +0530 [thread overview]
Message-ID: <48A9AF1D.5050700@in.ibm.com> (raw)
In-Reply-To: <18594.14443.340604.693747@cargo.ozlabs.ibm.com>
Hi Paul,
I can't boot zImage with your patches. I'm getting the following error
message from prom_init.c
Error: You can't boot a kdump kernel from OF!
This is due to the check:
if (PHYSICAL_START > 0)
prom_panic("Error: You can't boot a kdump kernel from OF!\n");
where PHYSICAL_START is kernstart_addr, and this variable needs to be
referred through RELOC macro
But even after commenting the above check, I am not able to boot zImage.
<snip boot message>
Building dt structure...
Device tree strings 0x0000000002ce4000 -> 0×0000000002ce5034
Device tree struct 0×0000000002ce6000 -> 0×0000000002cf0000
Calling quiesce …
returning from prom_init
<snip>
and the system hangs
It has CONFIG_RELOCATABLE set, (CONFIG_CRASH_DUMP is not set).
I even tried booting zImage through netboot, it also fails at the same
place.
If you need, I can give the .config I use.
Regards,
Mohan.
Paul Mackerras wrote:
> The following series of patches implement support for a relocatable
> kernel by building it as a position-independent executable (PIE).
> When the linker is given the -pie flag, it creates an executable that
> contains dynamic relocations which can be used to relocate the image
> at boot time for any desired base address. This patch series adds a
> CONFIG_RELOCATABLE config option for 64-bit which links the kernel
> with -pie and arranges to process the relocations in early boot.
>
> With the first 4 patches applied, a relocatable kernel will still copy
> itself down to real address 0. The last patch changes things so that
> a relocatable kernel will run wherever it was loaded. This last patch
> is pretty much just a proof of concept since it doesn't do anything to
> ensure appropriate alignment of the base address (the base address
> needs to be 16kB aligned). We probably want to work out whether we
> are a kdump kernel and run in-place if so, or copy down to 0 if not.
>
> Paul.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2008-08-18 17:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 1:27 [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support Paul Mackerras
2008-08-13 1:28 ` [PATCH 1/5] powerpc: Move interrupt handler code to the beginning of head_64.S Paul Mackerras
2008-08-13 1:29 ` [PATCH 2/5] powerpc: Make it possible to move the interrupt handlers away from the kernel Paul Mackerras
2008-08-13 1:30 ` [PATCH 3/5] powerpc: Only use LOAD_REG_IMMEDIATE for constants on 64-bit Paul Mackerras
2008-08-13 1:36 ` [PATCH 4/5] powerpc: Make the 64-bit kernel as a position-independent executable Paul Mackerras
2008-08-19 16:20 ` Geert Uytterhoeven
2008-08-20 6:34 ` Paul Mackerras
2008-08-13 1:38 ` [PATCH 5/5] powerpc: Run relocatable kernel where it's loaded Paul Mackerras
2008-08-18 17:19 ` Mohan Kumar M [this message]
2008-08-19 1:43 ` [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support Paul Mackerras
2008-08-19 5:35 ` Mohan Kumar M
2008-08-19 6:47 ` Paul Mackerras
2008-08-19 8:11 ` Mohan Kumar M
2008-08-28 12:12 ` David Woodhouse
2008-08-28 12:18 ` Kumar Gala
2008-08-29 6:16 ` Paul Mackerras
2008-08-28 12:26 ` Geert Uytterhoeven
2008-08-29 5:40 ` Paul Mackerras
2008-08-29 6:34 ` David Miller
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=48A9AF1D.5050700@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.