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
22 matches
Mail list logo
