From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <mingo@redhat.com>, <konrad.wilk@oracle.com>,
<yinghai@kernel.org>, <tglx@linutronix.de>, <joe.jin@oracle.com>,
<hpa@zytor.com>
Subject: 答复: [PATCH] Initialize max_pfn_mapped as initial ident mapping size for x86_64
Date: Sun, 4 Mar 2012 23:49:31 -0800 (PST) [thread overview]
Message-ID: <d493264b-7da0-41bd-b0bc-219b1a180f10@default> (raw)
----- zhenzhong.duan@oracle.com 写道:
> It's better to initialize max_pfn_mapped as initial ident
> mapping size but not initial kernel map size for x86_64.
> This is also in accordance with i386 code.
>
> It lead to page tables allocation to as high as 1G for
> init_memory_mapping,
> this will allow larger crashkernel reservation.
>
> Tested on HP DL980G7, it can reserve more than 521MiB space for kdump
> kernel now.
> http://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=13405
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
> Tested-by: Dawei Pang <dawei.pang@hp.com>
> ---
> arch/x86/kernel/head64.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
> index 3a3b779..3beb94f 100644
> --- a/arch/x86/kernel/head64.c
> +++ b/arch/x86/kernel/head64.c
> @@ -77,7 +77,7 @@ void __init x86_64_start_kernel(char *
> real_mode_data)
> /* Make NULL pointers segfault */
> zap_identity_mappings();
>
> - max_pfn_mapped = KERNEL_IMAGE_SIZE >> PAGE_SHIFT;
> + max_pfn_mapped = PUD_PAGE_SIZE >> PAGE_SHIFT;
>
> for (i = 0; i < NUM_EXCEPTION_VECTORS; i++) {
> #ifdef CONFIG_EARLY_PRINTK
> --
> 1.7.3
Hmm, any comment is welcome
thanks
zduan
next reply other threads:[~2012-03-05 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 7:49 Zhenzhong Duan [this message]
2012-03-05 16:40 ` Greg KH
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=d493264b-7da0-41bd-b0bc-219b1a180f10@default \
--to=zhenzhong.duan@oracle.com \
--cc=hpa@zytor.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®