mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Dave Young <dyoung@redhat.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	linux@arm.linux.org.uk, vgoyal@redhat.com
Subject: Re: [PATCH v2] kdump x86: fix total mem size calculation for reservation
Date: Sat, 10 Mar 2012 16:38:29 +0800	[thread overview]
Message-ID: <4F5B1305.4080306@gmail.com> (raw)
In-Reply-To: <20120310045632.GA4214@darkstar.redhat.com>

On 03/10/2012 12:56 PM, Dave Young wrote:
> crashkernel reservation need know the total memory size. Current get_total_mem
> simply use max_pfn - min_low_pfn. It is wrong because it will including
> memory holes in the middle.
>
> Especially for kvm guest with memory>  0xe0000000, there's below in qemu code:
> qemu split memory as below:
>      if (ram_size>= 0xe0000000 ) {
>          above_4g_mem_size = ram_size - 0xe0000000;
>          below_4g_mem_size = 0xe0000000;
>      } else {
>          below_4g_mem_size = ram_size;
>      }
> So for 4G mem guest, seabios will insert a 512M usable region beyond of 4G.
> Thus in above case max_pfn - min_low_pfn will be more than original memsize.
>
> Fixing this issue by using memblock_phys_mem_size() to get the total memsize.
>
> [v1 ->  v2]: refresh the patch based on latest linus tree
>

Looks good to my eyes,

Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>

Can you post the result of crashkernel after this patch to convince people?

Thanks.

  reply	other threads:[~2012-03-10  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  8:30 [PATCH] " Dave Young
2012-03-10  3:27 ` Cong Wang
2012-03-10  4:32   ` Dave Young
2012-03-10  4:56   ` [PATCH v2] " Dave Young
2012-03-10  8:38     ` Cong Wang [this message]
2012-03-10 16:06       ` Dave Young

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=4F5B1305.4080306@gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=vgoyal@redhat.com \
    --cc=x86@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

Powered by JetHome