* [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
@ 2008-10-01 18:25 ` Mohan Kumar M
0 siblings, 0 replies; 6+ messages in thread
From: Mohan Kumar M @ 2008-10-01 18:25 UTC (permalink / raw)
To: paulus; +Cc: ppcdev, kexec
One of the relocatable kernel support patches assumes that the target
address will be 0. But for kdump kernels (without relocation support) it
will be 32MB. The following patch fixes this issue.
Fix kdump kernel issue
Kdump kernel without relocation support needs to be moved to
PHYSICAL_START (ie 32MB) instead of 0. This patch fixes this
issue.
Signed-off-by: Mohan Kumar M <mohan@in.ibm.com>
---
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..8934500 100644
--- a/arch/powerpc/kernel/head_64.S
+++ b/arch/powerpc/kernel/head_64.S
@@ -1395,7 +1395,7 @@ _STATIC(__after_prom_start)
*
* Note: This process overwrites the OF exception vectors.
*/
- li r3,0 /* target addr */
+ LOAD_REG_IMMEDIATE(r3, PHYSICAL_START) /* target addr */
mr. r4,r26 /* In some cases the loader may */
beq 9f /* have already put us at zero */
lis r5,(copy_to_here - _stext)@ha
--
1.5.5.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply related [flat|nested] 6+ messages in thread
* [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
@ 2008-10-01 18:25 ` Mohan Kumar M
0 siblings, 0 replies; 6+ messages in thread
From: Mohan Kumar M @ 2008-10-01 18:25 UTC (permalink / raw)
To: paulus; +Cc: ppcdev, kexec
One of the relocatable kernel support patches assumes that the target
address will be 0. But for kdump kernels (without relocation support) it
will be 32MB. The following patch fixes this issue.
Fix kdump kernel issue
Kdump kernel without relocation support needs to be moved to
PHYSICAL_START (ie 32MB) instead of 0. This patch fixes this
issue.
Signed-off-by: Mohan Kumar M <mohan@in.ibm.com>
---
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..8934500 100644
--- a/arch/powerpc/kernel/head_64.S
+++ b/arch/powerpc/kernel/head_64.S
@@ -1395,7 +1395,7 @@ _STATIC(__after_prom_start)
*
* Note: This process overwrites the OF exception vectors.
*/
- li r3,0 /* target addr */
+ LOAD_REG_IMMEDIATE(r3, PHYSICAL_START) /* target addr */
mr. r4,r26 /* In some cases the loader may */
beq 9f /* have already put us at zero */
lis r5,(copy_to_here - _stext)@ha
--
1.5.5.1
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
2008-10-01 18:25 ` Mohan Kumar M
@ 2008-10-09 5:32 ` Paul Mackerras
-1 siblings, 0 replies; 6+ messages in thread
From: Paul Mackerras @ 2008-10-09 5:32 UTC (permalink / raw)
To: mohan; +Cc: ppcdev, kexec
Mohan Kumar M writes:
> One of the relocatable kernel support patches assumes that the target
> address will be 0. But for kdump kernels (without relocation support) it
> will be 32MB. The following patch fixes this issue.
>
> Fix kdump kernel issue
>
> Kdump kernel without relocation support needs to be moved to
> PHYSICAL_START (ie 32MB) instead of 0. This patch fixes this
> issue.
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?
I don't think we want to try to support two different modes of
operation for a kdump kernel, and I don't see any value in continuing
to support PHYSICAL_START > 0 for 64-bit non-relocatable kernels.
(And when we can make 32-bit PIE kernels, I'll be making the same
statement about 32-bit. :)
Paul.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
@ 2008-10-09 5:32 ` Paul Mackerras
0 siblings, 0 replies; 6+ messages in thread
From: Paul Mackerras @ 2008-10-09 5:32 UTC (permalink / raw)
To: mohan; +Cc: ppcdev, kexec
Mohan Kumar M writes:
> One of the relocatable kernel support patches assumes that the target
> address will be 0. But for kdump kernels (without relocation support) it
> will be 32MB. The following patch fixes this issue.
>
> Fix kdump kernel issue
>
> Kdump kernel without relocation support needs to be moved to
> PHYSICAL_START (ie 32MB) instead of 0. This patch fixes this
> issue.
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?
I don't think we want to try to support two different modes of
operation for a kdump kernel, and I don't see any value in continuing
to support PHYSICAL_START > 0 for 64-bit non-relocatable kernels.
(And when we can make 32-bit PIE kernels, I'll be making the same
statement about 32-bit. :)
Paul.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
2008-10-09 5:32 ` Paul Mackerras
@ 2008-10-09 16:34 ` Mohan Kumar M
-1 siblings, 0 replies; 6+ messages in thread
From: Mohan Kumar M @ 2008-10-09 16:34 UTC (permalink / raw)
To: Paul Mackerras; +Cc: ppcdev, kexec
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. But if nobody needs the legacy kdump, we can make kdump depend on
relocatable
Regards,
Mohan.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] Fix kdump kernel hang issue with relocatable kernel patches
@ 2008-10-09 16:34 ` Mohan Kumar M
0 siblings, 0 replies; 6+ messages in thread
From: Mohan Kumar M @ 2008-10-09 16:34 UTC (permalink / raw)
To: Paul Mackerras; +Cc: ppcdev, kexec
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. But if nobody needs the legacy kdump, we can make kdump depend on
relocatable
Regards,
Mohan.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-10-09 16:34 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-01 18:25 [PATCH] Fix kdump kernel hang issue with relocatable kernel patches Mohan Kumar M
2008-10-01 18:25 ` Mohan Kumar M
2008-10-09 5:32 ` Paul Mackerras
2008-10-09 5:32 ` Paul Mackerras
2008-10-09 16:34 ` Mohan Kumar M
2008-10-09 16:34 ` Mohan Kumar M
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.