[PATCH] makedumpfile: Claim to support 2.6.27

According to the changelog and my tests, 2.6.27 kernel is supported. Express that in the LATEST_VERSION check. Signed-off-by: Bernhard Walle [EMAIL PROTECTED] diff --git a/makedumpfile.h b/makedumpfile.h --- a/makedumpfile.h +++ b/makedumpfile.h @@ -436,7 +436,7 @@ #define KVER_MIN_SHIFT 16

[PATCH 2/8] x86 kdump: Move crashing_cpu assignment to nmi_shootdown_cpus()

This variable will be moved to non-kdump-specific code. Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/kernel/crash.c |8 +--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c index 6047542..ed2f0f9 100644 ---

[PATCH 8/8] x86: Disable IRQs before doing anything on nmi_shootdown_cpus()

We need to know on which CPU we are running on, and we don't want to be preempted while doing this. Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/kernel/reboot.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/x86/kernel/reboot.c

[PATCH 1/8] x86 kdump: Extract kdump-specific code from crash_nmi_callback()

The NMI CPU-halting code will be used on non-kdump cases, also (e.g. emergency_reboot when virtualization is enabled). Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/kernel/crash.c | 31 --- 1 files changed, 20 insertions(+), 11 deletions(-) diff

[PATCH 5/8] x86 kdump: Make nmi_shootdown_cpus() non-static

Add prototype to asm/reboot.h. Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/include/asm/reboot.h |5 + arch/x86/kernel/crash.c |3 +-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/reboot.h b/arch/x86/include/asm/reboot.h

[PATCH 4/8] x86 kdump: Make kdump_nmi_callback() a function ptr on crash_nmi_callback()

The reboot code will use a different function on crash_nmi_callback(). Adding a function pointer parameter to nmi_shootdown_cpus() for that. Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/kernel/crash.c | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) diff

Re: [PATCH 0/8] Make nmi_shootdown_cpus() usable by non-kdump code

* Eduardo Habkost [EMAIL PROTECTED] wrote: Hi, Ingo, As tip/master is a moving target, I am splitting the previous kdump/reboot virtualization-disable code series[1] into smaller series so the simpler parts can be included sooner. This first series is just for making

[PATCH] Always use 64 bit addresses for the firmware memory map

I had a problem that on i386 without PAE enabled the firmware memory map was wrong because a 64 bit address has been truncated: -0009f400 (System RAM) 0009f400-000a (reserved) fec1-fec11000 (reserved)

Re: [PATCH] Always use 64 bit addresses for the firmware memory map

* H. Peter Anvin [2008-11-12 11:59]: I want to make sure, though, that we don't just end up pushing the truncation further down in the code. Well, I think that interface should export the BIOS memmap as provided. Since E820 does provide 64 bit addresses, that should get exported. It should

[PATCH 3/8] x86 kdump: Create kdump_nmi_shootdown_cpus()

For the kdump-specific code that was living on nmi_shootdown_cpus(). Signed-off-by: Eduardo Habkost [EMAIL PROTECTED] --- arch/x86/kernel/crash.c | 11 +-- 1 files changed, 9 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c index

Re: [PATCH] Always use 64 bit addresses for the firmware memory map

Bernhard Walle wrote: * H. Peter Anvin [2008-11-12 11:59]: I want to make sure, though, that we don't just end up pushing the truncation further down in the code. Well, I think that interface should export the BIOS memmap as provided. Since E820 does provide 64 bit addresses, that should

Re: [PATCH] Always use 64 bit addresses for the firmware memory map

Jeremy Fitzhardinge wrote: resource_size_t should always be 64-bit on PAE now. Yes, but this would affect non-PAE kernels too. -hpa ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec

Re: [PATCH] Always use 64 bit addresses for the firmware memory map

H. Peter Anvin wrote: Jeremy Fitzhardinge wrote: resource_size_t should always be 64-bit on PAE now. Yes, but this would affect non-PAE kernels too. Yeah, I overlooked the comment about non-PAE. Should we just make resource_size_t 64 bits all the time? Or ignore inaccessible

Re: [PATCH] Always use 64 bit addresses for the firmware memory map

Jeremy Fitzhardinge wrote: H. Peter Anvin wrote: Jeremy Fitzhardinge wrote: resource_size_t should always be 64-bit on PAE now. Yes, but this would affect non-PAE kernels too. Yeah, I overlooked the comment about non-PAE. Should we just make resource_size_t 64 bits all the

Comprehensive Healthcare Directory

Fully Licensed Physicians in the USA Physicians in many different specialties Over a dozen sortable fields Now priced at: $393 {}{}{} Order this week and get the additional data below for free {}{}{} ++ Hospitals ++ Nursing Homes ++ Visiting Nurses RN's ++ Chiropractors reply to::