linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Suzuki Poulose <suzuki@in.ibm.com>
To: Josh Boyer <jwboyer@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	Josh Poimboeuf <jpoimboe@linux.vnet.ibm.com>,
	linux ppc dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v4 0/7] Kudmp support for PPC440x
Date: Sat, 10 Dec 2011 10:31:52 +0530	[thread overview]
Message-ID: <4EE2E7C0.2040102@in.ibm.com> (raw)
In-Reply-To: <20111209114148.15616.15996.stgit@suzukikp.in.ibm.com>

On 12/09/11 17:13, Suzuki K. Poulose wrote:
> The following series implements:
>
>   * Generic framework for relocatable kernel on PPC32, based on processing
>     the dynamic relocation entries.
>   * Relocatable kernel support for 44x
>   * Kdump support for 44x. Doesn't support 47x yet, as the kexec
>     support is missing.
>
> Changes from V3:
>
>   * Added a new config - NONSTATIC_KERNEL - to group different types of relocatable
>     kernel. (Suggested by: Josh Boyer)
>   * Added supported ppc relocation types in relocs_check.pl for verifying the
>     relocations used in the kernel.
>
> Changes from V2:
>
>   * Renamed old style mapping based RELOCATABLE on BookE to DYNAMIC_MEMSTART.
>     Suggested by: Scott Wood
>   * Added support for DYNAMIC_MEMSTART on PPC440x
>   * Reverted back to RELOCATABLE and RELOCATABLE_PPC32 from RELOCATABLE_PPC32_PIE
>     for relocation based on processing dynamic reloc entries for PPC32.
>   * Ensure the modified instructions are flushed and the i-cache invalidated at
>     the end of relocate(). - Reported by : Josh Poimboeuf
>
> Changes from V1:
>
>   * Splitted patch 'Enable CONFIG_RELOCATABLE for PPC44x' to move some
>     of the generic bits to a new patch.
>   * Renamed RELOCATABLE_PPC32 to RELOCATABLE_PPC32_PIE and provided options to
>     retained old style mapping. (Suggested by: Scott Wood)
>   * Added support for avoiding the overlapping of uncompressed kernel
>     with boot wrapper for PPC images.
>
> The patches are based on -next tree for ppc.
>
> I have tested these patches on Ebony, Sequoia and Virtex(QEMU Emulated).
> I haven't tested the RELOCATABLE bits on PPC_47x yet, as I don't have access
> to one. However, RELOCATABLE should work fine there as we only depend on the
> runtime address and the XLAT entry setup by the boot loader. It would be great if
> somebody could test these patches on a 47x.
>
>
> ---

Updated diffstats:

Suzuki K. Poulose (7):
       [boot] Change the load address for the wrapper to fit the kernel
       [44x] Enable CRASH_DUMP for 440x
       [44x] Enable CONFIG_RELOCATABLE for PPC44x
       [ppc] Define virtual-physical translations for RELOCATABLE
       [ppc] Process dynamic relocations for kernel
       [44x] Enable DYNAMIC_MEMSTART for 440x
       [booke] Rename mapping based RELOCATABLE to DYNAMIC_MEMSTART for BookE


  arch/powerpc/Kconfig                          |   46 +++++-
  arch/powerpc/Makefile                         |    6 -
  arch/powerpc/boot/wrapper                     |   20 ++
  arch/powerpc/configs/44x/iss476-smp_defconfig |    2
  arch/powerpc/include/asm/kdump.h              |    4
  arch/powerpc/include/asm/page.h               |   89 ++++++++++-
  arch/powerpc/kernel/Makefile                  |    2
  arch/powerpc/kernel/crash_dump.c              |    4
  arch/powerpc/kernel/head_44x.S                |  105 +++++++++++++
  arch/powerpc/kernel/head_fsl_booke.S          |    2
  arch/powerpc/kernel/machine_kexec.c           |    2
  arch/powerpc/kernel/prom_init.c               |    2
  arch/powerpc/kernel/reloc_32.S                |  207 +++++++++++++++++++++++++
  arch/powerpc/kernel/vmlinux.lds.S             |    8 +
  arch/powerpc/mm/44x_mmu.c                     |    2
  arch/powerpc/mm/init_32.c                     |    7 +
  arch/powerpc/relocs_check.pl                  |    7 +
  17 files changed, 489 insertions(+), 26 deletions(-)
  create mode 100644 arch/powerpc/kernel/reloc_32.S


Thanks
Suzuki

      parent reply	other threads:[~2011-12-10  5:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 11:43 [PATCH v4 0/7] Kudmp support for PPC440x Suzuki K. Poulose
2011-12-09 11:43 ` [PATCH v4 1/7] [booke] Rename mapping based RELOCATABLE to DYNAMIC_MEMSTART for BookE Suzuki K. Poulose
2011-12-09 11:47 ` [PATCH v4 2/7] [44x] Enable DYNAMIC_MEMSTART for 440x Suzuki K. Poulose
2011-12-09 11:47 ` [PATCH v4 3/7] [ppc] Process dynamic relocations for kernel Suzuki K. Poulose
2011-12-09 13:40   ` Josh Boyer
2011-12-10  2:35     ` Suzuki Poulose
2011-12-10  2:37   ` [UPDATED] " Suzuki K. Poulose
2011-12-10 20:02     ` Segher Boessenkool
2011-12-13  2:24       ` Suzuki Poulose
2011-12-09 11:47 ` [PATCH v4 4/7] [ppc] Define virtual-physical translations for RELOCATABLE Suzuki K. Poulose
2011-12-09 11:48 ` [PATCH v4 5/7] [44x] Enable CONFIG_RELOCATABLE for PPC44x Suzuki K. Poulose
2011-12-09 11:48 ` [PATCH v4 6/7] [44x] Enable CRASH_DUMP for 440x Suzuki K. Poulose
2011-12-09 11:48 ` [PATCH v4 7/7] [boot] Change the load address for the wrapper to fit the kernel Suzuki K. Poulose
2011-12-10  5:01 ` Suzuki Poulose [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=4EE2E7C0.2040102@in.ibm.com \
    --to=suzuki@in.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=jpoimboe@linux.vnet.ibm.com \
    --cc=jwboyer@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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 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).