Re: [PATCH] kdump/kexec: calculate note size at compile time
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that this value is
in fact too small. The particular setup I was using actually
needs 1172 bytes. This lead to very tedious failure mode
where the tail of one elf note would overwrite the head of
another if they ended up being alocated sequentially by kmalloc,
which was often the case.
It seems to me that a far better approach is to caclculate the size
that the area needs to be. This patch does just that.
If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
is needed then this should be as easy as making MAX_NOTE_BYTES
larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
However, I think that the approach in this patch is a much more robust
idea.
Signed-off-by: Simon Horman <[EMAIL PROTECTED]>
Acked-by: Vivek Goyal <[EMAIL PROTECTED]>
---
As suggested by Milton Miller
* Changed KEXEC_NOTE_NAME_BYTES to KEXEC_CORE_NOTE_NAME_BYTES and
KEXEC_NOTE_DESC_BYTES to KEXEC_CORE_NOTE_DESC_BYTES to avoid
a possible name-clash if additional notes are added in the future.
* Use KEXEC_CORE_NOTE_NAME in the definition of KEXEC_CORE_NOTE_NAME_BYTES
* Clean up comment about the notes area being a lit of notes
arch/ia64/kernel/crash.c|2 +-
include/asm-arm/kexec.h |2 --
include/asm-i386/kexec.h|2 --
include/asm-ia64/kexec.h|2 --
include/asm-mips/kexec.h|2 --
include/asm-powerpc/kexec.h |2 --
include/asm-s390/kexec.h|2 --
include/asm-sh/kexec.h |2 --
include/asm-x86_64/kexec.h |2 --
include/linux/kexec.h | 17 -
kernel/kexec.c |4 ++--
11 files changed, 19 insertions(+), 20 deletions(-)
Index: linux-2.6/include/asm-ia64/kexec.h
===
--- linux-2.6.orig/include/asm-ia64/kexec.h 2007-04-02 21:50:46.0
+0900
+++ linux-2.6/include/asm-ia64/kexec.h 2007-04-03 18:14:39.0 +0900
@@ -14,8 +14,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_IA_64
-#define MAX_NOTE_BYTES 1024
-
#define kexec_flush_icache_page(page) do { \
unsigned long page_addr = (unsigned long)page_address(page); \
flush_icache_range(page_addr, page_addr + PAGE_SIZE); \
Index: linux-2.6/include/linux/kexec.h
===
--- linux-2.6.orig/include/linux/kexec.h2007-04-02 21:50:46.0
+0900
+++ linux-2.6/include/linux/kexec.h 2007-04-03 18:19:03.0 +0900
@@ -7,6 +7,8 @@
#include
#include
#include
+#include
+#include
#include
/* Verify architecture specific macros are defined */
@@ -31,6 +33,19 @@
#error KEXEC_ARCH not defined
#endif
+#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
+#define KEXEC_CORE_NOTE_NAME "CORE"
+#define KEXEC_CORE_NOTE_NAME_BYTES ALIGN(sizeof(KEXEC_CORE_NOTE_NAME), 4)
+#define KEXEC_CORE_NOTE_DESC_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
+/*
+ * The per-cpu notes area is a list of notes terminated by a "NULL"
+ * note header. For kdump, the code in vmcore.c runs in the context
+ * of the second kernel to combine them into one note.
+ */
+#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
+ KEXEC_CORE_NOTE_NAME_BYTES +\
+ KEXEC_CORE_NOTE_DESC_BYTES )
+
/*
* This structure is used to hold the arguments that are used when loading
* kernel binaries.
@@ -136,7 +151,7 @@
/* Location of a reserved region to hold the crash kernel.
*/
extern struct resource crashk_res;
-typedef u32 note_buf_t[MAX_NOTE_BYTES/4];
+typedef u32 note_buf_t[KEXEC_NOTE_BYTES/4];
extern note_buf_t *crash_notes;
Index: linux-2.6/include/asm-arm/kexec.h
===
--- linux-2.6.orig/include/asm-arm/kexec.h 2007-04-02 21:50:46.0
+0900
+++ linux-2.6/include/asm-arm/kexec.h 2007-04-03 18:14:39.0 +0900
@@ -16,8 +16,6 @@
#ifndef __ASSEMBLY__
-#define MAX_NOTE_BYTES 1024
-
struct kimage;
/* Provide a dummy definition to avoid build failures. */
static inline void crash_setup_regs(struct pt_regs *newregs,
Index: linux-2.6/include/asm-i386/kexec.h
===
--- linux-2.6.orig/include/asm-i386/kexec.h 2007-04-02 21:50:46.0
+0900
+++ linux-2.6/include/asm-i386/kexec.h 2007-04-03 18:14:39.0 +0900
@@ -47,8 +47,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_386
-#define MAX_NOTE_BYTES 1024
-
/* CPU does not save ss and esp on stack if execution is already
* running in kernel mode at the time of NM
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Mon, Apr 02, 2007 at 01:48:48PM +0900, Simon Horman wrote:
> On Thu, Mar 29, 2007 at 05:41:45PM -0700, Andrew Morton wrote:
> > On Thu, 29 Mar 2007 12:30:59 +0900
> > Simon Horman <[EMAIL PROTECTED]> wrote:
> >
> > > [PATCH] kdump/kexec: calculate note size at compile time
> >
> > i386 allmodconfig, gcc-4.1.0:
> >
> > In file included from init/initramfs.c:508:
> > include/linux/kexec.h:148: error: variable-size type declared outside of
> > any function
>
> Hi,
>
> this problem appears to be caused by the use of strlen() inside the
> definition of KEXEC_NOTE_NAME_BYTES. I have removed this and the patch
> now compiles cleanly using gcc 4.1.2 on i386 allmodconfig, which
> previously gave the same error as above.
Hi,
Here is a further update to this patch which uses
sizeof(KEXEC_NOTE_NAME_BYTES) as suggested by Milton Miller.
It also adds a comment describing why space for two struct elf_note
is needed, as that question has come up a few times.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that this value is
in fact too small. The particular setup I was using actually
needs 1172 bytes. This lead to very tedious failure mode
where the tail of one elf note would overwrite the head of
another if they ended up being alocated sequentially by kmalloc,
which was often the case.
It seems to me that a far better approach is to caclculate the size
that the area needs to be. This patch does just that.
If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
is needed then this should be as easy as making MAX_NOTE_BYTES
larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
However, I think that the approach in this patch is a much more robust
idea.
Acked-by: Vivek Goyal <[EMAIL PROTECTED]>
Signed-off-by: Simon Horman <[EMAIL PROTECTED]>
include/asm-arm/kexec.h |2 --
include/asm-i386/kexec.h|2 --
include/asm-ia64/kexec.h|2 --
include/asm-mips/kexec.h|2 --
include/asm-powerpc/kexec.h |2 --
include/asm-s390/kexec.h|2 --
include/asm-sh/kexec.h |2 --
include/asm-x86_64/kexec.h |2 --
include/linux/kexec.h | 10 +-
9 files changed, 9 insertions(+), 17 deletions(-)
Index: linux-2.6/include/asm-ia64/kexec.h
===
--- linux-2.6.orig/include/asm-ia64/kexec.h 2007-04-02 14:53:00.0
+0900
+++ linux-2.6/include/asm-ia64/kexec.h 2007-04-02 14:53:07.0 +0900
@@ -14,8 +14,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_IA_64
-#define MAX_NOTE_BYTES 1024
-
#define kexec_flush_icache_page(page) do { \
unsigned long page_addr = (unsigned long)page_address(page); \
flush_icache_range(page_addr, page_addr + PAGE_SIZE); \
Index: linux-2.6/include/linux/kexec.h
===
--- linux-2.6.orig/include/linux/kexec.h2007-04-02 14:53:00.0
+0900
+++ linux-2.6/include/linux/kexec.h 2007-04-02 17:17:08.0 +0900
@@ -7,6 +7,8 @@
#include
#include
#include
+#include
+#include
#include
/* Verify architecture specific macros are defined */
@@ -31,6 +33,18 @@
#error KEXEC_ARCH not defined
#endif
+#define KEXEC_NOTE_NAME "CORE"
+#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
+#define KEXEC_NOTE_NAME_BYTES ALIGN(sizeof("CORE"), 4) /* N.B: Includes '\0' */
+#define KEXEC_NOTE_DESC_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
+/* The notes are read and combined by the code in vmcore.c running
+ * in the second-kernel after kdump is performed. This code
+ * expects the notes area to be a list of notes, terminated
+ * by a "NULL" note header. The "* 2" below is to provide space
+ * for the terminating note header */
+#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
+ KEXEC_NOTE_NAME_BYTES + KEXEC_NOTE_DESC_BYTES )
+
/*
* This structure is used to hold the arguments that are used when loading
* kernel binaries.
@@ -136,7 +150,7 @@
/* Location of a reserved region to hold the crash kernel.
*/
extern struct resource crashk_res;
-typedef u32 note_buf_t[MAX_NOTE_BYTES/4];
+typedef u32 note_buf_t[KEXEC_NOTE_BYTES/4];
extern note_buf_t *crash_notes;
Index: linux-2.6/include/asm-arm/kexec.h
===
--- linux-2.6.orig/include/asm-arm/kexec.h 2007-04-02 14:53:00.0
+0900
+++ linux-2.6/include/asm-arm/kexec.h 2007-04-02 14:53:07.0 +0900
@@ -16,8 +16,6 @@
#ifndef __ASSEMBLY__
-#define MAX_NOTE_BYTES 1024
-
struct kimage;
/* Provide a dummy
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Thu, Mar 29, 2007 at 05:41:45PM -0700, Andrew Morton wrote:
> On Thu, 29 Mar 2007 12:30:59 +0900
> Simon Horman <[EMAIL PROTECTED]> wrote:
>
> > [PATCH] kdump/kexec: calculate note size at compile time
>
> i386 allmodconfig, gcc-4.1.0:
>
> In file included from init/initramfs.c:508:
> include/linux/kexec.h:148: error: variable-size type declared outside of any
> function
Hi,
this problem appears to be caused by the use of strlen() inside the
definition of KEXEC_NOTE_NAME_BYTES. I have removed this and the patch
now compiles cleanly using gcc 4.1.2 on i386 allmodconfig, which
previously gave the same error as above.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that this value is
in fact too small. The particular setup I was using actually
needs 1172 bytes. This lead to very tedious failure mode
where the tail of one elf note would overwrite the head of
another if they ended up being alocated sequentially by kmalloc,
which was often the case.
It seems to me that a far better approach is to caclculate the size
that the area needs to be. This patch does just that.
If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
is needed then this should be as easy as making MAX_NOTE_BYTES
larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
However, I think that the approach in this patch is a much more robust
idea.
Acked-by: Vivek Goyal <[EMAIL PROTECTED]>
Signed-off-by: Simon Horman <[EMAIL PROTECTED]>
include/asm-arm/kexec.h |2 --
include/asm-i386/kexec.h|2 --
include/asm-ia64/kexec.h|2 --
include/asm-mips/kexec.h|2 --
include/asm-powerpc/kexec.h |2 --
include/asm-s390/kexec.h|2 --
include/asm-sh/kexec.h |2 --
include/asm-x86_64/kexec.h |2 --
include/linux/kexec.h | 10 +-
9 files changed, 9 insertions(+), 17 deletions(-)
Index: linux-2.6/include/asm-ia64/kexec.h
===
--- linux-2.6.orig/include/asm-ia64/kexec.h 2007-04-02 11:56:00.0
+0900
+++ linux-2.6/include/asm-ia64/kexec.h 2007-04-02 13:21:15.0 +0900
@@ -14,8 +14,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_IA_64
-#define MAX_NOTE_BYTES 1024
-
#define kexec_flush_icache_page(page) do { \
unsigned long page_addr = (unsigned long)page_address(page); \
flush_icache_range(page_addr, page_addr + PAGE_SIZE); \
Index: linux-2.6/include/linux/kexec.h
===
--- linux-2.6.orig/include/linux/kexec.h2007-04-02 11:56:00.0
+0900
+++ linux-2.6/include/linux/kexec.h 2007-04-02 13:45:31.0 +0900
@@ -7,6 +7,8 @@
#include
#include
#include
+#include
+#include
#include
/* Verify architecture specific macros are defined */
@@ -31,6 +33,12 @@
#error KEXEC_ARCH not defined
#endif
+#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
+#define KEXEC_NOTE_NAME_BYTES 8 /* ALIGN(strlen("CORE") + 1, 4) */
+#define KEXEC_NOTE_DESC_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
+#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
+ KEXEC_NOTE_NAME_BYTES + KEXEC_NOTE_DESC_BYTES )
+
/*
* This structure is used to hold the arguments that are used when loading
* kernel binaries.
@@ -136,7 +144,7 @@
/* Location of a reserved region to hold the crash kernel.
*/
extern struct resource crashk_res;
-typedef u32 note_buf_t[MAX_NOTE_BYTES/4];
+typedef u32 note_buf_t[KEXEC_NOTE_BYTES/4];
extern note_buf_t *crash_notes;
Index: linux-2.6/include/asm-arm/kexec.h
===
--- linux-2.6.orig/include/asm-arm/kexec.h 2007-04-02 11:56:00.0
+0900
+++ linux-2.6/include/asm-arm/kexec.h 2007-04-02 13:21:15.0 +0900
@@ -16,8 +16,6 @@
#ifndef __ASSEMBLY__
-#define MAX_NOTE_BYTES 1024
-
struct kimage;
/* Provide a dummy definition to avoid build failures. */
static inline void crash_setup_regs(struct pt_regs *newregs,
Index: linux-2.6/include/asm-i386/kexec.h
===
--- linux-2.6.orig/include/asm-i386/kexec.h 2007-04-02 11:56:00.0
+0900
+++ linux-2.6/include/asm-i386/kexec.h 2007-04-02 13:21:15.0 +0900
@@ -47,8 +47,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_386
-#define MAX_NOTE_BYTES 1024
-
/* CPU does not save ss and esp on stack if execution is already
* running in kernel mode at the time of NMI occurrence. This code
* fixes it.
Index: linux-2.6/include/asm-mips/kexe
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Thu, Mar 29, 2007 at 05:41:45PM -0700, Andrew Morton wrote: > On Thu, 29 Mar 2007 12:30:59 +0900 > Simon Horman <[EMAIL PROTECTED]> wrote: > > > [PATCH] kdump/kexec: calculate note size at compile time > > i386 allmodconfig, gcc-4.1.0: > > In file included from init/initramfs.c:508: > include/linux/kexec.h:148: error: variable-size type declared outside of any > function Thanks, I will look into this. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Thu, 29 Mar 2007 12:30:59 +0900 Simon Horman <[EMAIL PROTECTED]> wrote: > [PATCH] kdump/kexec: calculate note size at compile time i386 allmodconfig, gcc-4.1.0: In file included from init/initramfs.c:508: include/linux/kexec.h:148: error: variable-size type declared outside of any function - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Thu, Mar 29, 2007 at 09:14:21AM +0530, Vivek Goyal wrote: > On Thu, Mar 29, 2007 at 12:30:59PM +0900, Simon Horman wrote: > > Hi, > > > > this is a(nother) minor update to this patch. > > Explanation below. > > > > -- > > Horms > > H: http://www.vergenet.net/~horms/ > > W: http://www.valinux.co.jp/en/ > > > > [PATCH] kdump/kexec: calculate note size at compile time > > > > Currently the size of the per-cpu region reserved to save crash > > notes is set by the per-architecture value MAX_NOTE_BYTES. Which > > in turn is currently set to 1024 on all supported architectures. > > > > While testing ia64 I recently discovered that this value is > > in fact too small. The particular setup I was using actually > > needs 1172 bytes. This lead to very tedious failure mode > > where the tail of one elf note would overwrite the head of > > another if they ended up being alocated sequentially by kmalloc, > > which was often the case. > > > > It seems to me that a far better approach is to caclculate the size > > that the area needs to be. This patch does just that. > > > > If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X) > > is needed then this should be as easy as making MAX_NOTE_BYTES > > larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice. > > However, I think that the approach in this patch is a much more robust > > idea. > > > > Update I: > > > > Changed KEXEC_NOTE_HEAD_BYTES to KEXEC_NOTE_DESC_BYTES in line > > with the name of the relevant field in struct elf_note > > > > Update II: > > > > * Use KEXEC_NOTE_NAME instead of "CORE" in kernel/kexec.c and > > arch/ia64/kernel/crash.c just to be extra sure that the data > > used to calculate the size, and the data stuffed into the reserved > > area is the same. > > > > Incidently, the ia64 code really ought to use the generic code. > > I am working on a patch for this. But it is not urgent. > > > > Looks good. Another patch to make ia64 also use generic kexec code > for note generation would be nice. Thanks, I will make it so :-) -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Thu, Mar 29, 2007 at 12:30:59PM +0900, Simon Horman wrote: > Hi, > > this is a(nother) minor update to this patch. > Explanation below. > > -- > Horms > H: http://www.vergenet.net/~horms/ > W: http://www.valinux.co.jp/en/ > > [PATCH] kdump/kexec: calculate note size at compile time > > Currently the size of the per-cpu region reserved to save crash > notes is set by the per-architecture value MAX_NOTE_BYTES. Which > in turn is currently set to 1024 on all supported architectures. > > While testing ia64 I recently discovered that this value is > in fact too small. The particular setup I was using actually > needs 1172 bytes. This lead to very tedious failure mode > where the tail of one elf note would overwrite the head of > another if they ended up being alocated sequentially by kmalloc, > which was often the case. > > It seems to me that a far better approach is to caclculate the size > that the area needs to be. This patch does just that. > > If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X) > is needed then this should be as easy as making MAX_NOTE_BYTES > larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice. > However, I think that the approach in this patch is a much more robust > idea. > > Update I: > > Changed KEXEC_NOTE_HEAD_BYTES to KEXEC_NOTE_DESC_BYTES in line > with the name of the relevant field in struct elf_note > > Update II: > > * Use KEXEC_NOTE_NAME instead of "CORE" in kernel/kexec.c and > arch/ia64/kernel/crash.c just to be extra sure that the data > used to calculate the size, and the data stuffed into the reserved > area is the same. > > Incidently, the ia64 code really ought to use the generic code. > I am working on a patch for this. But it is not urgent. > Looks good. Another patch to make ia64 also use generic kexec code for note generation would be nice. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kdump/kexec: calculate note size at compile time
Hi,
this is a(nother) minor update to this patch.
Explanation below.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that this value is
in fact too small. The particular setup I was using actually
needs 1172 bytes. This lead to very tedious failure mode
where the tail of one elf note would overwrite the head of
another if they ended up being alocated sequentially by kmalloc,
which was often the case.
It seems to me that a far better approach is to caclculate the size
that the area needs to be. This patch does just that.
If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
is needed then this should be as easy as making MAX_NOTE_BYTES
larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
However, I think that the approach in this patch is a much more robust
idea.
Update I:
Changed KEXEC_NOTE_HEAD_BYTES to KEXEC_NOTE_DESC_BYTES in line
with the name of the relevant field in struct elf_note
Update II:
* Use KEXEC_NOTE_NAME instead of "CORE" in kernel/kexec.c and
arch/ia64/kernel/crash.c just to be extra sure that the data
used to calculate the size, and the data stuffed into the reserved
area is the same.
Incidently, the ia64 code really ought to use the generic code.
I am working on a patch for this. But it is not urgent.
* Added Ack from Vivek, which was actually for the update I version
of the patch. If this is wrong, please tell me.
Acked-by: Vivek Goyal <[EMAIL PROTECTED]>
Signed-off-by: Simon Horman <[EMAIL PROTECTED]>
arch/ia64/kernel/crash.c|2 +-
include/asm-arm/kexec.h |2 --
include/asm-i386/kexec.h|2 --
include/asm-ia64/kexec.h|2 --
include/asm-mips/kexec.h|2 --
include/asm-powerpc/kexec.h |2 --
include/asm-s390/kexec.h|2 --
include/asm-sh/kexec.h |2 --
include/asm-x86_64/kexec.h |2 --
include/linux/kexec.h | 11 ++-
kernel/kexec.c |2 +-
11 files changed, 12 insertions(+), 19 deletions(-)
Index: linux-2.6/include/asm-ia64/kexec.h
===
--- linux-2.6.orig/include/asm-ia64/kexec.h 2007-03-28 18:50:25.0
+0900
+++ linux-2.6/include/asm-ia64/kexec.h 2007-03-29 12:19:10.0 +0900
@@ -14,8 +14,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_IA_64
-#define MAX_NOTE_BYTES 1024
-
#define kexec_flush_icache_page(page) do { \
unsigned long page_addr = (unsigned long)page_address(page); \
flush_icache_range(page_addr, page_addr + PAGE_SIZE); \
Index: linux-2.6/include/linux/kexec.h
===
--- linux-2.6.orig/include/linux/kexec.h2007-03-28 18:50:25.0
+0900
+++ linux-2.6/include/linux/kexec.h 2007-03-29 12:19:10.0 +0900
@@ -7,6 +7,8 @@
#include
#include
#include
+#include
+#include
#include
/* Verify architecture specific macros are defined */
@@ -31,6 +33,13 @@
#error KEXEC_ARCH not defined
#endif
+#define KEXEC_NOTE_NAME "CORE"
+#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
+#define KEXEC_NOTE_NAME_BYTES ALIGN(strlen(KEXEC_NOTE_NAME) + 1, 4)
+#define KEXEC_NOTE_DESC_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
+#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
+ KEXEC_NOTE_NAME_BYTES + KEXEC_NOTE_DESC_BYTES )
+
/*
* This structure is used to hold the arguments that are used when loading
* kernel binaries.
@@ -136,7 +145,7 @@
/* Location of a reserved region to hold the crash kernel.
*/
extern struct resource crashk_res;
-typedef u32 note_buf_t[MAX_NOTE_BYTES/4];
+typedef u32 note_buf_t[KEXEC_NOTE_BYTES/4];
extern note_buf_t *crash_notes;
Index: linux-2.6/include/asm-arm/kexec.h
===
--- linux-2.6.orig/include/asm-arm/kexec.h 2007-03-28 18:50:25.0
+0900
+++ linux-2.6/include/asm-arm/kexec.h 2007-03-29 12:19:10.0 +0900
@@ -16,8 +16,6 @@
#ifndef __ASSEMBLY__
-#define MAX_NOTE_BYTES 1024
-
struct kimage;
/* Provide a dummy definition to avoid build failures. */
static inline void crash_setup_regs(struct pt_regs *newregs,
Index: linux-2.6/include/asm-i386/kexec.h
===
--- linux-2.6.orig/include/asm-i386/kexec.h 2007-03-28 18:50:25.0
+0900
+++ linux-2.6/include/asm-i386/kexec.h 2007-03-29 12:19:10.0 +0900
@@ -47,8 +47,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_386
-#define MAX_NOTE_BYTES 1024
-
/* CPU doe
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Wed, Mar 28, 2007 at 04:13:20PM +0900, Horms wrote: [..] > > DESC is probably a better name that BODY here, I meant to update > that before posting. An updated version is below. > > > > +#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \ > > > > Why are we multiplying KEXEC_NOTE_HEAD_BYTES with 2? > > The way that the note merging code works in vmcore it assumes that > the area is a list of notes. And there is a terminating note that > has all the header values set to 0, and nothing else. So the time 2 > is for the space to store the terminating note. > Ok.. Got it. Looks fine to me. Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Wed, Mar 28, 2007 at 12:13:53PM +0530, Vivek Goyal wrote:
> On Wed, Mar 28, 2007 at 03:18:58PM +0900, Simon Horman wrote:
> > Currently the size of the per-cpu region reserved to save crash
> > notes is set by the per-architecture value MAX_NOTE_BYTES. Which
> > in turn is currently set to 1024 on all supported architectures.
> >
> > While testing ia64 I recently discovered that this value is
> > in fact too small. The particular setup I was using actually
> > needs 1172 bytes. This lead to very tedious failure mode
> > where the tail of one elf note would overwrite the head of
> > another if they ended up being alocated sequentially by kmalloc,
> > which was often the case.
> >
> > It seems to me that a far better approach is to caclculate the size
> > that the area needs to be. This patch does just that.
> >
> > If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
> > is needed then this should be as easy as making MAX_NOTE_BYTES
> > larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
> > However, I think that the approach in this patch is a much more robust idea.
> >
>
> Makes sense to me. Calculating the size based on elf_prstatus is better
> than hardcoding it to some value.
>
> A minor query is inlined below.
>
> [..]
> > ===
> > --- linux-2.6.orig/include/linux/kexec.h2007-03-28 09:42:14.0
> > +0900
> > +++ linux-2.6/include/linux/kexec.h 2007-03-28 12:32:50.0 +0900
> > @@ -7,6 +7,8 @@
> > #include
> > #include
> > #include
> > +#include
> > +#include
> > #include
> >
> > /* Verify architecture specific macros are defined */
> > @@ -31,6 +33,13 @@
> > #error KEXEC_ARCH not defined
> > #endif
> >
> > +#define KEXEC_NOTE_NAME "CORE"
> > +#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4)
> > +#define KEXEC_NOTE_NAME_BYTES ALIGN(strlen(KEXEC_NOTE_NAME) + 1, 4)
> > +#define KEXEC_NOTE_BODY_BYTES ALIGN(sizeof(struct elf_prstatus), 4)
DESC is probably a better name that BODY here, I meant to update
that before posting. An updated version is below.
> > +#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \
>
> Why are we multiplying KEXEC_NOTE_HEAD_BYTES with 2?
The way that the note merging code works in vmcore it assumes that
the area is a list of notes. And there is a terminating note that
has all the header values set to 0, and nothing else. So the time 2
is for the space to store the terminating note.
This structure isn't entirely neccessary, and if we were to modify the
mergeing code in vmcore (which runs in the second kernel) it could be
changed.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
[PATCH] kdump/kexec: calculate note size at compile time
Currently the size of the per-cpu region reserved to save crash
notes is set by the per-architecture value MAX_NOTE_BYTES. Which
in turn is currently set to 1024 on all supported architectures.
While testing ia64 I recently discovered that this value is
in fact too small. The particular setup I was using actually
needs 1172 bytes. This lead to very tedious failure mode
where the tail of one elf note would overwrite the head of
another if they ended up being alocated sequentially by kmalloc,
which was often the case.
It seems to me that a far better approach is to caclculate the size
that the area needs to be. This patch does just that.
If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X)
is needed then this should be as easy as making MAX_NOTE_BYTES
larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice.
However, I think that the approach in this patch is a much more robust idea.
Signed-off-by: Simon Horman <[EMAIL PROTECTED]>
include/asm-arm/kexec.h |2 --
include/asm-i386/kexec.h|2 --
include/asm-ia64/kexec.h|2 --
include/asm-mips/kexec.h|2 --
include/asm-powerpc/kexec.h |2 --
include/asm-s390/kexec.h|2 --
include/asm-sh/kexec.h |2 --
include/asm-x86_64/kexec.h |2 --
include/linux/kexec.h | 11 ++-
9 files changed, 10 insertions(+), 17 deletions(-)
Index: linux-2.6/include/asm-ia64/kexec.h
===
--- linux-2.6.orig/include/asm-ia64/kexec.h 2007-03-28 15:57:15.0
+0900
+++ linux-2.6/include/asm-ia64/kexec.h 2007-03-28 15:57:17.0 +0900
@@ -14,8 +14,6 @@
/* The native architecture */
#define KEXEC_ARCH KEXEC_ARCH_IA_64
-#define MAX_NOTE_BYTES 1024
-
#define kexec_flush_icache_page(page) do { \
unsigned long page_addr = (unsigned long)page_address(page); \
flush_icache_range(page_addr, page_addr + PAGE_SIZE); \
Index: linux-2.6/include/linux/kexec.h
===
--- linux-2.6.orig/include/linux/kexec.h2007-03-28 15:57:15.0
+0900
+++ linux-2.6/include
Re: [PATCH] kdump/kexec: calculate note size at compile time
On Wed, Mar 28, 2007 at 03:18:58PM +0900, Simon Horman wrote: > Currently the size of the per-cpu region reserved to save crash > notes is set by the per-architecture value MAX_NOTE_BYTES. Which > in turn is currently set to 1024 on all supported architectures. > > While testing ia64 I recently discovered that this value is > in fact too small. The particular setup I was using actually > needs 1172 bytes. This lead to very tedious failure mode > where the tail of one elf note would overwrite the head of > another if they ended up being alocated sequentially by kmalloc, > which was often the case. > > It seems to me that a far better approach is to caclculate the size > that the area needs to be. This patch does just that. > > If a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X) > is needed then this should be as easy as making MAX_NOTE_BYTES > larger in arch/asm-ia64/kexec.h. Perhaps 2048 would be a good choice. > However, I think that the approach in this patch is a much more robust idea. > Makes sense to me. Calculating the size based on elf_prstatus is better than hardcoding it to some value. A minor query is inlined below. [..] > === > --- linux-2.6.orig/include/linux/kexec.h 2007-03-28 09:42:14.0 > +0900 > +++ linux-2.6/include/linux/kexec.h 2007-03-28 12:32:50.0 +0900 > @@ -7,6 +7,8 @@ > #include > #include > #include > +#include > +#include > #include > > /* Verify architecture specific macros are defined */ > @@ -31,6 +33,13 @@ > #error KEXEC_ARCH not defined > #endif > > +#define KEXEC_NOTE_NAME "CORE" > +#define KEXEC_NOTE_HEAD_BYTES ALIGN(sizeof(struct elf_note), 4) > +#define KEXEC_NOTE_NAME_BYTES ALIGN(strlen(KEXEC_NOTE_NAME) + 1, 4) > +#define KEXEC_NOTE_BODY_BYTES ALIGN(sizeof(struct elf_prstatus), 4) > +#define KEXEC_NOTE_BYTES ( (KEXEC_NOTE_HEAD_BYTES * 2) + \ Why are we multiplying KEXEC_NOTE_HEAD_BYTES with 2? Thanks Vivek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
