All,
I'm trying to determine how kexec'ing works on 64 bit powerpc. When allocating
a region for the kexec'ed kernel is it ever the same as the currently running
kernel or do you always boot the kexec'ed kernel from a different memory
region? I understand that a crash kernel will be in a
I'm trying to determine how kexec'ing works on 64 bit powerpc. When
allocating a region for the kexec'ed kernel is it ever the same as the
currently running kernel or do you always boot the kexec'ed kernel
from a different memory region? I understand that a crash kernel will
be in a different
On Tue, May 18, 2010 at 09:30:32AM +1000, Michael Neuling wrote:
In message 4becbe89.3020...@ozlabs.org you wrote:
add_dyn_reconf_usable_mem_property() iterates over memory spans
in /ibm,dynamic-reconfiguration-memory/ibm,dynamic-memory and intersects
these with usablemem_rgns ranges.
-by: Michael Neuling mi...@neuling.org
---
kexec/arch/ppc64/fs2dt.c | 82 +++-
--
1 files changed, 70 insertions(+), 12 deletions(-)
diff --git a/kexec/arch/ppc64/fs2dt.c b/kexec/arch/ppc64/fs2dt.c
index 762bf04..4400f13 100644
--- a/kexec/arch/ppc64
the fixed-sized arrays from
add_dyn_reconf_usable_mem_property() and add_usable_mem_property(), in lieu of
malloc/realloc/free.
Signed-off-by: Matt Evans m...@ozlabs.org
---
kexec/arch/ppc64/fs2dt.c | 82 +++---
1 files changed, 70 insertions(+), 12 deletions
-by: Matt Evans m...@ozlabs.org
---
kexec/arch/ppc64/fs2dt.c | 66 +
1 files changed, 54 insertions(+), 12 deletions(-)
diff --git a/kexec/arch/ppc64/fs2dt.c b/kexec/arch/ppc64/fs2dt.c
index 762bf04..7470132 100644
--- a/kexec/arch/ppc64/fs2dt.c
+++ b
in add_usable_mem_property, in lieu of malloc/realloc/fr
ee.
Thanks matt!
Acked-by: Michael Neuling mi...@neuling.org
Signed-off-by: Matt Evans m...@ozlabs.org
---
kexec/arch/ppc64/fs2dt.c | 66 +---
-
1 files changed, 54 insertions(+), 12 deletions(-)
diff
On Mon, May 10, 2010 at 02:55:03PM +1000, Michael Neuling wrote:
In message 4be78e06.6080...@ozlabs.org you wrote:
ppc64's fs2dt used to use a fixed-size array into which the device tree
was parsed. There was no bounds checking, so with a large device tree other
heap data ended up
, 'dt_reserve', to check whether there's enough spa
ce
left prior to writing data to the array. If not, the array is realloced.
Signed-off-by: Matt Evans m...@ozlabs.org
FWIW...
Ack-by: Michael Neuling mi...@neuling.org
(also added linuxppc-...@ozlabs.org to CC list)
---
kexec/arch/ppc64/fs2dt.c
On Wed, May 05, 2010 at 11:46:25AM +0400, Maxim Uvarov wrote:
2010/5/5 Simon Horman ho...@verge.net.au
On Wed, May 05, 2010 at 01:35:21PM +1000, Michael Neuling wrote:
In message 20100505023316.gf13...@verge.net.au you wrote:
On Wed, May 05, 2010 at 11:48:53AM +1000, Michael
2010/5/5 Simon Horman ho...@verge.net.au
On Wed, May 05, 2010 at 01:35:21PM +1000, Michael Neuling wrote:
In message 20100505023316.gf13...@verge.net.au you wrote:
On Wed, May 05, 2010 at 11:48:53AM +1000, Michael Neuling wrote:
6adc05c6e3fdbc8b9f5d915af78ca05d0a09cb17 some kexec
, effecting all other archs.
kexec/arch/ppc64/fs2dt.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: kexec-tools/kexec/arch/ppc64/fs2dt.c
===
--- kexec-tools.orig/kexec/arch/ppc64/fs2dt.c
+++ kexec-tools/kexec/arch
---
I've posted a second patch to fix the issue of changing one archs
Makefile, effecting all other archs.
kexec/arch/ppc64/fs2dt.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: kexec-tools/kexec/arch/ppc64/fs2dt.c
.
kexec/arch/ppc64/fs2dt.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: kexec-tools/kexec/arch/ppc64/fs2dt.c
===
--- kexec-tools.orig/kexec/arch/ppc64/fs2dt.c
+++ kexec-tools/kexec/arch/ppc64/fs2dt.c
@@ -357,7
-by: Michael Neuling mi...@neuling.org
---
I've posted a second patch to fix the issue of changing one archs
Makefile, effecting all other archs.
kexec/arch/ppc64/fs2dt.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: kexec-tools/kexec/arch/ppc64/fs2dt.c
On Wed, May 05, 2010 at 01:35:21PM +1000, Michael Neuling wrote:
In message 20100505023316.gf13...@verge.net.au you wrote:
On Wed, May 05, 2010 at 11:48:53AM +1000, Michael Neuling wrote:
6adc05c6e3fdbc8b9f5d915af78ca05d0a09cb17 some kexec MIPS
improvements broke pp64 as it turned on
it in the slave loop at 0
# skip cache flush, do we care?
bctr# start kernel
Index: kexec-tools/kexec/arch/ppc64/crashdump-ppc64.h
===
--- kexec-tools.orig/kexec/arch/ppc64
, not the usual case.
Index: kexec-tools/kexec/arch/ppc64/kexec-elf-ppc64.c
===
--- kexec-tools.orig/kexec/arch/ppc64/kexec-elf-ppc64.c 2008-10-22
06:14:48.0 -0500
+++ kexec-tools/kexec/arch/ppc64/kexec-elf-ppc64.c 2008-10
On Oct 22, 2008, at 3:39 PM, Milton Miller wrote:
Every time add_segment is called, the segments are sorted. If the
first
hole in memory is not big enough for the kernel then something besides
the kernel may be at
info-segment[0].
---
Found during custom environment testing with several
19 matches
Mail list logo
