Use pr_debug instead of printk
WARNING: Prefer [subsystem eg: netdev]_dbg([subsystem]dev, ... then
dev_dbg(dev, ... then pr_debug(... to printk(KERN_DEBUG ...
Signed-off-by: Mohan Kumar
---
drivers/cpuidle/cpuidle-powernv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Use pr_debug instead of printk
WARNING: Prefer [subsystem eg: netdev]_dbg([subsystem]dev, ...
then dev_dbg(dev, ... then pr_debug(... to printk(KERN_DEBUG ...
Signed-off-by: Mohan Kumar
---
drivers/cpuidle/cpuidle-pseries.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
se as 32MB, and it
may also fail in reserving memory for kdump kernel.
On 11/27/2009 12:56 AM, Bernhard Walle wrote:
M. Mohan Kumar schrieb:
On 11/26/2009 12:22 AM, Bernhard Walle wrote:
M. Mohan Kumar schrieb:
Reserve memory for kdump kernel within RMO region
When the kernel size exceeds
On 11/27/2009 12:56 AM, Bernhard Walle wrote:
M. Mohan Kumar schrieb:
On 11/26/2009 12:22 AM, Bernhard Walle wrote:
M. Mohan Kumar schrieb:
Reserve memory for kdump kernel within RMO region
When the kernel size exceeds 32MB(observed with some distros), memory
for kdump kernel can not be
On 11/26/2009 12:22 AM, Bernhard Walle wrote:
M. Mohan Kumar schrieb:
Reserve memory for kdump kernel within RMO region
When the kernel size exceeds 32MB(observed with some distros), memory
for kdump kernel can not be reserved as kdump kernel base is assumed to
be 32MB always. When the kernel
memory for kdump kernel anywhere in
the RMO region.
Signed-off-by: M. Mohan Kumar
---
arch/powerpc/kernel/machine_kexec.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/machine_kexec.c
b/arch/powerpc/kernel/machine_kexec.c
index
printng to hvc console.
Includes the changes suggested by Michael Ellerman
Signed-off-by: M. Mohan Kumar
---
kexec/arch/ppc64/fs2dt.c | 62 +++-
kexec/arch/ppc64/kexec-elf-ppc64.c |7
purgatory/arch/ppc64/Makefile |1 +
purga
> On Mon, Sep 07, 2009 at 10:44:07AM +0530, M. Mohan Kumar wrote:
> > Write to HVC terminal from purgatory code
> >
> > Current x86/x86-64 kexec-tools print the message "I'm in purgatory" to
> > serial console/VGA while executing the purgatory code. Impl
to hvc console.
Signed-off-by: M. Mohan Kumar
---
kexec/arch/ppc64/fs2dt.c | 47 +++-
kexec/arch/ppc64/kexec-elf-ppc64.c |7 +
kexec/arch/ppc64/kexec-ppc64.h |1 +
purgatory/arch/ppc64/Makefile |1 +
purgatory/arch/ppc6
immediately for system reset
exception and kdump kernel will be invoked (if its loaded). If kdump
kernel is not loaded, proceed with xmon
Signed-off-by: M. Mohan Kumar
---
arch/powerpc/xmon/xmon.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/xmo
[PATCH 2/2] Support R_PPC64_REL32 relocation type
gcc-4.4 compiler creates R_PPC64_REL32 relocation type in the ppc64
purgatory code. Add support to handle R_PPC64_REL32 relocation type.
Signed-off-by: M. Mohan Kumar
---
kexec/arch/ppc64/kexec-elf-rel-ppc64.c |4
1 files changed, 4
word, the struct memory must start on an 8 byte boundary. Force the
dtstruct variable to be always 8 bytes aligned.
Signed-off-by: M. Mohan Kumar
---
kexec/arch/ppc64/fs2dt.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kexec/arch/ppc64/fs2dt.c b/kexec/arch/ppc64
On Fri, Aug 07, 2009 at 08:05:49PM +0530, M. Mohan Kumar wrote:
> Hi,
>
> After enabling EARLY_DEBUG (and DEBUG in some of the files in
> arch/powerpc/kernel directory), without forcing the dtstruct variable to 8
> byte alignment:
>
> # ./kexec -e
> Starting new kernel
&
variable is not aligned to
8 byte variable. This problem is not seen with gcc-3.4. Is it compiler
issue? or bug in the code.
Regards,
M. Mohan Kumar.
On Fri, Aug 07, 2009 at 12:24:20AM +1000, Michael Ellerman wrote:
> On Wed, 2009-08-05 at 22:19 +0530, M. Mohan Kumar wrote:
> > Hi,
>
Hi,
When I align the dtstruct variable to 8 bytes, I am able to invoke kdump.
When the line
static unsigned dtstruct[TREEWORDS], *dt;
changed to
static unsigned dtstruct[TREEWORDS] __attribute__ ((aligned (8))), *dt;
kexec-tool works.
Regards,
M. Mohan Kumar
On Mon, Aug 03
On Wed, Jun 24, 2009 at 10:27:43AM +1000, Michael Ellerman wrote:
> On Tue, 2009-06-23 at 09:56 -0400, Neil Horman wrote:
> > On Tue, Jun 23, 2009 at 06:25:34PM +0530, M. Mohan Kumar wrote:
> > >
> > Well it definately looks like removing that variable had some code chan
On Wed, Jun 17, 2009 at 10:05:14AM -0400, Neil Horman wrote:
> On Wed, Jun 17, 2009 at 07:04:35PM +0530, M. Mohan Kumar wrote:
> > On Wed, Jun 17, 2009 at 09:04:13AM -0400, Neil Horman wrote:
> > > On Wed, Jun 17, 2009 at 10:26:35PM +1000, Michael Ellerman wrote:
> > &g
t that change is will likely provide clues to how the code has changed.
Neil, there was no code change in fs2dt.c
Regards,
M. Mohan Kumar
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
kernel to hang. After further investigation, I observed that if the putprops
function is not inlined, kexec/kdump kernel would work even after removing
the above lines.
This patch directs gcc to not inline the putprops function. Now we could
invoke kexec and kdump kernels.
Signed-off-by:
Do not inline putprops function
With the recent kexec-tools git tree, both kexec and kdump kernels hang (i.e
kexec -l and kexec -p respectively). This happened after the patch "ppc64:
cleanups" commit b43a84a31a4be6ed025c1bdef3bb1c3c12e01b16. I tried
reverting each hunk and then found out that ret
> On Fri, Jan 02, 2009 at 02:42:38PM -0600, Milton Miller wrote:
> > Follwing this mail are 5 patches for kexec userspace and two for the
> > kernel. The first fixes an array overflow and the second updates
> > userspace to the merged 2.6.28 kdump support. The remaining are
> > cleanups and warni
Enable RELOCATABLE option if user selects CRASH_DUMP option. Without this
patch user has to first select RELOCATABLE option and then has to enable
CRASH_DUMP option.
Signed-off-by: M. Mohan Kumar
---
arch/powerpc/Kconfig |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a
Enable RELOCATABLE option if user selects CRASH_DUMP option. Without this
patch user has to first select RELOCATABLE option and then has to enable
CRASH_DUMP option.
Signed-off-by: M. Mohan Kumar
---
arch/powerpc/Kconfig |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a
will be running
as a relocatable kernel.
Signed-off-by: M. Mohan Kumar
Signed-off-by: Milton Miller
---
kexec/arch/ppc64/crashdump-ppc64.h |2 ++
kexec/arch/ppc64/kexec-elf-ppc64.c | 17 +
purgatory/arch/ppc64/v2wrap.S | 25 -
3 files changed, 31
Milton Miller wrote:
On Oct 23, 2008, at 10:15 AM, Mohan Kumar M wrote:
Hi Milton,
My suggestions:
Milton Miller wrote:
i.e.,
[code snip 1]
lwz r7,__run_at_load-_stext(r26)
cmplwi cr0,r7,1/* kdump kernel ? - stay where we are */
bne 1f
add
Hi Milton,
My suggestions:
Milton Miller wrote:
The __kdump_flag ABI is overly constraining for future development.
As of 2.6.27, the kernel entry point has 4 constraints: Offset 0 is
the starting point for the master (boot) cpu (entered with r3 pointing
to the device tree structure), offse
Michael Ellerman wrote:
Does it? I see CONFIG_CRASH_DUMP depending on PPC64, so there is no
32-bit kdump possible. Or is someone working on it out-of-tree?
IIUC Anton Vorontsov is working on the 32-bit kdump kernel support.
Do you expect a function to do the checking in iommu.c?
You'd use
Michael Ellerman wrote:
Forwarded Message
The purgatory code compares the signature and sets the __kdump_flag in
head_64.S. During the boot up, kernel code checks __kdump_flag and if it
is set, the kernel will behave as relocatable kdump kernel. This kernel
will boot at the add
Paul Mackerras wrote:
Mohan Kumar M writes:
Support for relocatable kdump kernel
@@ -1401,9 +1414,21 @@ _STATIC(__after_prom_start)
beq 9f /* have already put us at zero */
li r6,0x100/* Start offset, the first 0x100
the changes suggested by Paul Mackerrass to avoid
GOT use and to avoid two copies of the code.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 14 ++---
arch/powerpc/Kconfig |8 ++-
arch/powerpc/include/asm/k
Hi Paul,
Thank you for the review. I will implement the changes you suggested and
send the patches.
Regards,
Mohan.
Mohan Kumar M writes:
Support for relocatable kdump kernel
[snip]
@@ -1384,7 +1392,15 @@ _STATIC(__after_prom_start)
/* process relocations for the final address
Paul Mackerras wrote:
Hmmm. Is there any reason to continue to support non-relocatable
64-bit kernels being kdump kernels? In other words, for 64-bit,
couldn't we make CONFIG_CRASH_DUMP depend on CONFIG_RELOCATABLE?
We wanted to support legacy kdump feature on 64 bit kernels for some
time.
t with the
patches that Mohan Kumar sent this week. But at this point
I don't see any particular need to break the patch up into
smaller pieices.
My patches are meant for PPC64 only. The patch implements support for
relocatable kdump kernel on PPC64 platform.
So I don't think Sebasti
Anton Vorontsov wrote:
On Tue, Sep 30, 2008 at 06:18:28PM +0530, Mohan Kumar M wrote:
Remove legacy kdump kernel build support
Hi,
I have submitted the patch to support relocatable kdump kernel with
retaining legacy kdump build support.
Regards,
Mohan.
Can we leave the legacy support
: Mohan Kumar M <[EMAIL PROTECTED]>
---
Documentation/kdump/kdump.txt | 14 ++--
arch/powerpc/Kconfig |4 +-
arch/powerpc/include/asm/kdump.h | 16
arch/powerpc/kernel/crash_dump.c |2 +
arch/powerpc/kernel/head_64.S
(ie 32MB) instead of 0. This patch fixes this
issue.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/head_64.S |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
index 84856be..8
.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
diff --git a/purgatory/arch/ppc64/v2wrap.S b/purgatory/arch/ppc64/v2wrap.S
index b3563de..f69dad2 100644
--- a/purgatory/arch/ppc64/v2wrap.S
+++ b/purgatory/arch/ppc64/v2wrap.S
@@ -45,6 +45,7 @@
orisrn,rn,[EMAIL PRO
boot at the address where it was loaded by kexec-tools ie at the
address reserved through crashkernel boot parameter.
Now for kdump, both CONFIG_RELOCATABLE and CONFIG_CRASH_DUMP should be
enabled and the same kernel can be used as production and kdump kernel.
Signed-off-by: Mohan Kumar M <[EM
-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig|2 -
arch/powerpc/include/asm/iommu.h|5
arch/powerpc/include/asm/kdump.h| 35 --
arch/powerpc/include/asm/page.h |1 -
arch/powerpc/kernel/c
Paul Mackerras wrote:
Mohan Kumar M writes:
Attaching the .config
Hmmm, your config works for me on a POWER6 partition here, whether I
netboot the zImage.pseries or boot it with yaboot. I wonder if your
toolchain is an older version. What is the output from ld --version
and gcc --version
Hi Paul,
Attaching the .config
Paul Mackerras wrote:
Mohan Kumar M writes:
If you need, I can give the .config I use.
Yes please, send it over.
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.27-rc1
# Mon Aug 18 14:24:37 2008
#
CONFIG_PP
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_S
Paul Mackerras wrote:
Mohan Kumar M writes:
Hi Paul,
Thanks for your comments.
I will update the patches as per your comment and will give a detailed
description for each patch.
Regards,
Mohan.
static inline int in_kernel_text(unsigned long addr)
{
- if (addr >= (unsig
Relocation support for kdump kernel
Add relocation kernel support for kdump kernel path.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/crash_dump.c | 19 +++
arch/powerpc/kernel/iommu.c|7 +--
arch/powerpc/
@got entries. So use LOAD_REG_IMMEDIATE macro
instead of LOAD_REG_ADDR macro for relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/include/asm/ppc_asm.h |4 ++
arch/powerpc/include/asm/prom.h|2 +
arch/powerpc/include/asm/sections.h
offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to the relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/reloc_apply.S | 242 +++
1 files change
relocation apply
code.
TODO:
Relocatable vmlinux image is built in arch/powerpc/boot as vmlinux.reloc.
But it should be built in top level directory of kernel source as vmlinux
instead of vmlinux.reloc
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig
As my scripts did wrong commit, I have posted wrong patches. I am posting
the patches 3,4 and 5 again. Sorry for the inconvenience.
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
Relocation support for kdump kernel
Add relocation kernel support for kdump kernel path.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/crash_dump.c | 19 +++
arch/powerpc/kernel/iommu.c|7 -
arch/powerpc/kernel/machine_k
@got entries. So use LOAD_REG_IMMEDIATE macro
instead of LOAD_REG_ADDR macro for relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/include/asm/ppc_asm.h |4 ++
arch/powerpc/include/asm/prom.h|2 +
arch/powerpc/include/asm/sections.h
offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to the relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/vmlinux.lds.S | 28
arch/powerp
relocation apply
code.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig | 15 ---
arch/powerpc/Makefile |9 +++--
arch/powerpc/boot/Makefile | 39 ---
3 files changed, 55 insertions(+), 8 del
type and this
information is appended to the normal vmlinux file by using the patch
relocation_build.patch
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/relocs.c | 820
1 files changed, 820 insertions(+), 0 deletions(-)
Hi,
Following five patches enable the "relocatable kernel" feature for
PPC64 kernels.
1. Extract list of relocation offsets.patch
2. Build files needed for relocation.patch
3. Apply relocation.patch
4. Relocation support.patch
5. Relocation support for kdump
Paul Mackerras wrote:
Mohan Kumar M writes:
diff --git a/arch/powerpc/boot/relocs.c b/arch/powerpc/boot/relocs.c
new file mode 100644
index 000..31ca903
Where did this file come from? Did you write it all yourself? If
not, then you need to credit the original author in the patch
Paul Mackerras wrote:
Mohan Kumar M writes:
@@ -714,7 +714,7 @@ _GLOBAL(enter_rtas)
stdr6,PACASAVEDMSR(r13)
/* Setup our real return addr */
- LOAD_REG_ADDR(r4,.rtas_return_loc)
+ LOAD_REG_IMMEDIATE(r4,.rtas_return_loc)
If LOAD_REG_ADDR doesn't
Use LOAD_REG_IMMEDIATE macros
This patch changes all LOAD_REG_ADDR macro calls to LOAD_REG_IMMEDIATE
to make sure that we load the correct address.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/entry_64.S |4 ++--
arch/powerpc/mm/hash_lo
Relocation support for kdump kernel
This patch adds relocation support for the kdump kernel path
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/crash_dump.c | 19 +++
arch/powerpc/kernel/iommu.c|7 -
arch/powerpc/
adding the relocation kernel base address.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/head_64.S | 53 ++-
arch/powerpc/kernel/machine_kexec_64.c |4 +-
arch/powerpc/kernel/prom_init.c| 27 ++--
arch/p
offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/reloc_apply.S | 229 +++
1 files change
relocation apply
code.
TODO:
Relocatable vmlinux image is built in arch/powerpc/boot as vmlinux.reloc.
But it should be built in top level directory of kernel source as vmlinux
instead of vmlinux.reloc
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/K
normal vmlinux file by using the patch
relocation_build.patch
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/relocs.c | 865
1 files changed, 865 insertions(+), 0 deletions(-)
create mode 100644 arch/powerpc/boot/relocs.c
Segher Boessenkool wrote:
This patch changes all LOAD_REG_ADDR macro calls to LOAD_REG_IMMEDIATE
to make sure that we load the correct address.
Did you figure out _why_ LOAD_REG_ADDR doesn't work? Using
LOAD_REG_IMMEDIATE is actually a step back, it makes the kernel
binary non-PIC. And LOAD_R
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
Relocation support
This patch changes all LOAD_REG_ADDR macro calls to LOAD_REG_IMMEDIATE
to make sure that we load the correct address. It also takes care of
when accessing absolute symbols in the code by adding the relocation
kernel base address.
Signed-off-by: Mohan Kumar M <[EMAIL PROTEC
offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/reloc_apply.S | 229
1 file changed, 229 inse
relocation apply
code.
TODO:
Relocatable vmlinux image is built in arch/powerpc/boot as vmlinux.reloc.
But it should be built in top level directory of kernel source as vmlinux
instead of vmlinux.reloc
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig
type and this
information is appended to the normal vmlinux file by using the patch
relocation_build.patch
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/boot/relocs.c | 865 +
1 file changed, 865 insertions(+)
Index: linux-
Hi,
Following four patches enable the "relocatable kernel" feature for
PPC64 kernels.
1. extract_relocation_info.patch
2. relocation_build.patch
3. apply_relocation.patch
4. relocation_support.patch
With the patchset, vmcore image of a crashed system can be capture
Relocation support
This patch changes all LOAD_REG_ADDR macro calls to LOAD_REG_IMMEDIATE
to make sure that we load the correct address. It also takes care of
when accessing absolute symbols in the code by adding the relocation
kernel base address.
Signed-off-by: Mohan Kumar M <[EMAIL PROTEC
offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/reloc_apply.S | 229 ++
1 file changed, 229 inse
relocation apply
code.
File make.reloc is used to build the relocatable kernel "vmlinux.reloc".
TODO:
I have not yet integrated building relocatable kernel with kernel
Makefile. I need help to integrate this into kernel build process.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTE
type and this
information is appended to the normal vmlinux file by using the patch
relocation_build.patch
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
arch/powerpc/relocs.c | 865 ++
1 file changed, 865 insertions(+)
Index: linux-
Hi,
Following four patches enable the "relocatable kernel" feature for
PPC64 kernels.
1. extract_relocation_info.patch
2. relocation_build.patch
3. apply_relocation.patch
4. relocation_support.patch
With the patchset, vmcore image of a crashed system can be capture
Relocation support
This patch changes all LOAD_REG_ADDR macro calls to LOAD_REG_IMMEDIATE
to make sure that we load the correct address. It also takes care of
absolute symbols access in the code by adding the relocation kernel base
address.
Signed-off-by: Mohan Kumar M <[EMAIL PROTEC
delta to each offset
in the list which was generated and appended by patch 1 and 2. After
updating all offsets, control is given to relocatable kernel.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
Index: linux-2.6.26-rc3/arch/powerpc/kernel/reloc_a
relocation apply
code.
File make.reloc is used to build the relocatable kernel "vmlinux.reloc".
TODO:
I have not yet integrated building relocatable kernel with kernel
Makefile. I need help to integrate this into kernel build process.
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTE
type and this
information is appended to the normal vmlinux file by using the patch
relocation_build.patch
Signed-off-by: Mohan Kumar M <[EMAIL PROTECTED]>
---
Index: linux-2.6.26-rc3/arch/powerpc/relocs.c
===
--- /dev/null
+++
Hi,
Following four patches enable the "relocatable kernel" feature for
PPC64 kernels.
1. extract_relocation_info.patch
2. relocation_build.patch
3. apply_relocation.patch
4. relocation_support.patch
With the patchset, vmcore image of a crashed system can be capture
Hi,
Following four patches enable the "relocatable kernel" feature for
PPC64 kernels.
1. extract_relocation_info.patch
2. relocation_build.patch
3. apply_relocation.patch
4. relocation_support.patch
With the patchset, vmcore image of a crashed system can be capture
80 matches
Mail list logo
