From: WANG Chao <chaowang@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org, horms@verge.net.au, linn@hp.com,
hpa@zytor.com, dyoung@redhat.com, trenn@suse.de
Subject: Re: [PATCH v7 0/9] kexec-tools, x86: E820 memmap pass for kdump
Date: Thu, 8 May 2014 19:31:27 +0800 [thread overview]
Message-ID: <20140508113127.GA10420@dhcp-17-89.nay.redhat.com> (raw)
In-Reply-To: <20140507144551.GC21048@redhat.com>
On 05/07/14 at 10:45am, Vivek Goyal wrote:
> Hi Chao,
>
> I was testing latest kexec-tools and noticed that I still see some
> memmap entries on command line. I think they are ACPI memory and data
> areas.
>
> memmap=32K#8192K memmap=960K#8256K memmap=96K#2062752K memmap=16K#2062948K
> memmap=32K#2096108K memmap=16K#2096140K
>
> Is there a reason why ACPI related entries should be passed through
> command line and not through bootparams memory map.
Good catch!
Sorry, I made a mistake in commit 91f5b9c ("kdump: pass e820
reserved region to 2nd kernel via e820 table or setup data").
I've sent a fix:
http://lists.infradead.org/pipermail/kexec/2014-May/011768.html
Please give it try. Thanks in advance.
WANG Chao
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-05-08 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 2:56 [PATCH v7 0/9] kexec-tools, x86: E820 memmap pass for kdump WANG Chao
2014-04-22 2:56 ` [PATCH v7 1/9] x86, cleanup: add extra arguments to add_memmap() and delete_memmap() WANG Chao
2014-04-22 2:56 ` [PATCH v7 2/9] x86, cleanup: add_memmap() only do alignment check on RANGE_RAM WANG Chao
2014-04-22 2:56 ` [PATCH v7 3/9] x86, cleanup: add other types of memory range for 2nd kernel boot to memmap_p WANG Chao
2014-04-22 2:56 ` [PATCH v7 4/9] x86, cleanup: use dbgprint_mem_range for memory range debugging WANG Chao
2014-04-22 2:56 ` [PATCH v7 5/9] x86, cleanup: increase CRASH_MAX_MEMMAP_NR up to 1024 WANG Chao
2014-04-22 2:56 ` [PATCH v7 6/9] x86, cleanup: Store crash memory ranges kexec_info WANG Chao
2014-04-22 2:56 ` [PATCH v7 7/9] x86, cleanup: kexec memory range .end to be inclusive WANG Chao
2014-04-22 2:56 ` [PATCH v7 8/9] x86: add --pass-memmap-cmdline option WANG Chao
2014-04-22 2:56 ` [PATCH v7 9/9] x86: Pass memory range via E820 for kdump WANG Chao
2014-04-22 4:37 ` [PATCH v7 0/9] kexec-tools, x86: E820 memmap pass " WANG Chao
2014-04-23 0:14 ` Simon Horman
2014-04-23 3:31 ` WANG Chao
2014-05-07 14:45 ` Vivek Goyal
2014-05-08 11:31 ` WANG Chao [this message]
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=20140508113127.GA10420@dhcp-17-89.nay.redhat.com \
--to=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linn@hp.com \
--cc=trenn@suse.de \
--cc=vgoyal@redhat.com \
/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