From: David Miller <davem@davemloft.net>
To: paulus@samba.org
Cc: linuxppc-dev@ozlabs.org, dwmw2@infradead.org
Subject: Re: [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support
Date: Thu, 28 Aug 2008 23:34:36 -0700 (PDT) [thread overview]
Message-ID: <20080828.233436.142799161.davem@davemloft.net> (raw)
In-Reply-To: <18615.35796.969180.162185@cargo.ozlabs.ibm.com>
From: Paul Mackerras <paulus@samba.org>
Date: Fri, 29 Aug 2008 15:40:36 +1000
> The main remaining substantial technical issue is how we detect very
> early on that we are a kdump kernel. I think the policy should be
> that the kernel copies itself down to 0 if it's not a kdump kernel and
> runs wherever it was loaded if it's a kdump kernel. The only way to
> tell whether we're a kdump kernel seems to be to look at the kernel
> command line, which is a little tricky to do in head_64.S when the
> command line is buried inside the DTB.
Why not put a key at a fixed location in the .text section or similar?
Then you can access it using PC relative addressing, and whatever
loads the kdump kernel can put an appropriate value there.
prev parent reply other threads:[~2008-08-29 6:34 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 ` [PATCH 0/5] Relocatable 64-bit kernel using linker PIE support Mohan Kumar M
2008-08-19 1:43 ` 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 [this message]
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=20080828.233436.142799161.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).