From: Mohan Kumar M <mohan@in.ibm.com>
To: benh@kernel.crashing.org
Cc: ppcdev <linuxppc-dev@ozlabs.org>, paulus@samba.org, miltonm@bga.com
Subject: Re: [RFC v3 PATCH 1/4] Extract list of relocation offsets
Date: Fri, 18 Jul 2008 11:02:16 +0530 [thread overview]
Message-ID: <48802AE0.30105@in.ibm.com> (raw)
In-Reply-To: <1216325187.7740.353.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Fri, 2008-07-18 at 00:10 +0530, Mohan Kumar M wrote:
>> Extract list of relocation offsets
>>
>> Extract list of offsets in the vmlinux file for which the relocation
>> delta has to be patched. Currently only following type of relocation
>> types are considered: R_PPC64_ADDR16_HI, R_PPC64_TOC and R_PPC64_ADDR64
>>
>> The offsets are sorted according to the relocation type and this
>> information is appended to the normal vmlinux file by using the patch
>> relocation_build.patch
>
> Please, provide an indication of what changed since the previous
> version of the patch to make the reviewer's life easier !
>
Hi,
Oops, I missed out the detailed change description. Thanks Ben for
pointing this.
Here is a change summary from v2 to v3:
PATCH 1:
The difference is relocs.c is moved to arch/powerpc/boot from arch/powerpc/
PATCH 2:
Relocation build support is now 90% integrated with kernel build
process. Earlier one has to run separately different make to build
vmlinux.reloc image. Required linker scripts are moved to
arch/powerpc/boot from arch/powerpc
PATCH 3:
The difference is reloc_apply.S is moved to arch/powerpc/boot from
arch/powerpc/
PATCH 4:
Enough care is taken when creating bolted mapping for kdump kernel. Now
it creates bolted mapping from 32MB to of size "crash kernel size" in
case of crash kernel.
Regards,
Mohan.
next prev parent reply other threads:[~2008-07-18 5:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 18:33 [RFC v3 PATCH 0/4] Relocatable kernel support for PPC64 Mohan Kumar M
2008-07-17 18:40 ` [RFC v3 PATCH 1/4] Extract list of relocation offsets Mohan Kumar M
2008-07-17 20:06 ` Benjamin Herrenschmidt
2008-07-18 5:32 ` Mohan Kumar M [this message]
2008-07-18 17:00 ` Milton Miller
2008-07-21 19:17 ` Mohan Kumar M
2008-07-22 6:29 ` Paul Mackerras
2008-07-22 7:58 ` Mohan Kumar M
2008-07-21 19:20 ` [RFC v3 PATCH 2/4] Build files needed for relocation Mohan Kumar M
2008-07-21 19:21 ` [RFC v3 PATCH 3/4] Apply relocation Mohan Kumar M
2008-07-21 19:23 ` [RFC v3 PATCH 4/4] Relocation support Mohan Kumar M
2008-07-21 19:25 ` [RFC v3 PATCH 5/4] Relocation support for kdump kernel Mohan Kumar M
2008-07-21 19:26 ` [RFC v3 PATCH 6/4] Use LOAD_REG_IMMEDIATE macros Mohan Kumar M
2008-07-22 2:03 ` Paul Mackerras
2008-07-22 4:37 ` Mohan Kumar M
2008-07-22 6:37 ` Paul Mackerras
2008-07-22 17:13 ` Segher Boessenkool
2008-07-17 18:42 ` [RFC v3 PATCH 2/4] Build files needed for relocation support Mohan Kumar M
2008-07-17 18:45 ` [RFC v3 PATCH 3/4] Apply relocation info to vmlinux Mohan Kumar M
2008-07-17 18:48 ` [RFC v3 PATCH 4/4] Relocation support Mohan Kumar M
2008-07-18 17:48 ` Segher Boessenkool
2008-07-21 9:11 ` Mohan Kumar M
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=48802AE0.30105@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--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).