Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: WANG Chao <chaowang@redhat.com>
Cc: kexec@lists.infradead.org, horms@verge.net.au,
	ebiederm@xmission.com, hpa@zytor.com, dyoung@redhat.com,
	trenn@suse.de
Subject: Re: [PATCH 2/4] x86: Store memory ranges globally used for crash kernel to boot into
Date: Thu, 13 Feb 2014 16:46:19 -0500	[thread overview]
Message-ID: <20140213214619.GL30844@redhat.com> (raw)
In-Reply-To: <1392297055-31934-3-git-send-email-chaowang@redhat.com>

On Thu, Feb 13, 2014 at 09:10:53PM +0800, WANG Chao wrote:

[..]
> @@ -230,6 +231,8 @@ static int get_crash_memory_ranges(struct memory_range **range, int *ranges,
>  		/* Only Dumping memory of type System RAM. */
>  		if (memcmp(str, "System RAM\n", 11) == 0) {
>  			type = RANGE_RAM;
> +		} else if (memcmp(str, "reserved\n", 9) == 0) {
> +			type = RANGE_RESERVED;

Hi Chao,

Can we take up the issue of passing reserved ranges to second kernel in
a separate patchset. I had noticed higher memory usage due to that and
it might have been something else.

It might be easier to handle one thing at a time. Let us first start
passing the memory range we pass on command line through bootparams and
once that gets merged and stablizes, write a patchset to start passing
reserved memory ranges if need be.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-02-13 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 13:10 [PATCH 0/4] kexec-tools, x86: E820 memmap pass for kdump WANG Chao
2014-02-13 13:10 ` [PATCH 1/4] add macro dbgprint_mem_range WANG Chao
2014-02-13 20:35   ` Vivek Goyal
2014-02-14  6:31     ` WANG Chao
2014-02-13 13:10 ` [PATCH 2/4] x86: Store memory ranges globally used for crash kernel to boot into WANG Chao
2014-02-13 21:46   ` Vivek Goyal [this message]
2014-02-14  6:30     ` WANG Chao
2014-02-13 13:10 ` [PATCH 3/4] x86: add --pass-memmap-cmdline option WANG Chao
2014-02-13 13:10 ` [PATCH] x86: Pass memory range via E820 for kdump WANG Chao

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=20140213214619.GL30844@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=trenn@suse.de \
    /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