All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: fastboot-bounces@lists.osdl.org
Subject: [PATCH] kdump : Support kernels having 64k page size.
Date: Wed, 06 Sep 2006 05:56:24 +0530	[thread overview]
Message-ID: <44FE15B0.3030909@in.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 167 bytes --]

The following  kernel patch [ along with a patch to kexec tools posted 
seperately ]
is required to generate proper core files using kdump on ppc64.

Thanks
-Sachin



[-- Attachment #2: ppc64-kexec-tools-64k-page-support --]
[-- Type: text/plain, Size: 663 bytes --]

* Generate proper core files using kdump on ppc64 with 64k page support.

Signed-off-by: Sachin Sant <sachinp@in.ibm.com>
---

diff -Naurp a/include/asm-powerpc/kdump.h b/include/asm-powerpc/kdump.h
--- a/include/asm-powerpc/kdump.h	2006-08-31 03:01:13.000000000 +0530
+++ b/include/asm-powerpc/kdump.h	2006-08-31 05:49:13.000000000 +0530
@@ -7,7 +7,7 @@
 /* How many bytes to reserve at zero for kdump. The reserve limit should
  * be greater or equal to the trampoline's end address.
  * Reserve to the end of the FWNMI area, see head_64.S */
-#define KDUMP_RESERVE_LIMIT	0x8000
+#define KDUMP_RESERVE_LIMIT	max(0x8000, PAGE_SIZE)
 
 #ifdef CONFIG_CRASH_DUMP
 

             reply	other threads:[~2006-09-06  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  0:26 Sachin P. Sant [this message]
2006-09-06  2:59 ` [PATCH] kdump : Support kernels having 64k page size Michael Ellerman
2006-09-06  6:13   ` Haren Myneni
2006-09-07  0:51     ` Benjamin Herrenschmidt
2006-09-08  1:00       ` Sachin P. Sant
2006-09-08  1:08         ` Benjamin Herrenschmidt
2006-09-08  2:29           ` Sachin P. Sant

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=44FE15B0.3030909@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=fastboot-bounces@lists.osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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 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.