| Date | Mon, 14 Jan 2013 10:18:39 -0800 | Subject | Re: [PATCH v7u1 27/31] x86, kdump: remove crashkernel range find limit for 64bit | From | Yinghai Lu <> |
| |
On Mon, Jan 14, 2013 at 7:43 AM, Borislav Petkov <bp@alien8.de> wrote: > On Thu, Jan 03, 2013 at 04:48:47PM -0800, Yinghai Lu wrote: >> Now kexeced kernel/ramdisk could be above 4g, so remove 896 limit for >> 64bit. >> >> Signed-off-by: Yinghai Lu <yinghai@kernel.org> >> --- >> arch/x86/kernel/setup.c | 4 +--- >> 1 file changed, 1 insertion(+), 3 deletions(-) >> >> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c >> index c58497e..6adbc45 100644 >> --- a/arch/x86/kernel/setup.c >> +++ b/arch/x86/kernel/setup.c >> @@ -501,13 +501,11 @@ static void __init memblock_x86_reserve_range_setup_data(void) >> /* >> * Keep the crash kernel below this limit. On 32 bits earlier kernels >> * would limit the kernel to the low 512 MiB due to mapping restrictions. >> - * On 64 bits, kexec-tools currently limits us to 896 MiB; increase this >> - * limit once kexec-tools are fixed. > > Does this mean that kexec-tools has been fixed too?
with the patcheset that i sent to kexec-tools mailing list.
|