Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Chao <chaowang@redhat.com>
To: horms@verge.net.au, dyoung@redhat.com, linn@hp.com,
	vgoyal@redhat.com, hpa@zytor.com, trenn@suse.de
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH v7 0/9] kexec-tools, x86: E820 memmap pass for kdump
Date: Tue, 22 Apr 2014 12:37:51 +0800	[thread overview]
Message-ID: <20140422043751.GD4564@dhcp-17-89.nay.redhat.com> (raw)
In-Reply-To: <1398135407-30142-1-git-send-email-chaowang@redhat.com>

On 04/22/14 at 10:56am, WANG Chao wrote:
> Hi, All
> 
> This patchset enables passing memory map via E820 map on x86 platform instead
> of memmap=exactmap. It's a better design and will solve the following problem
> so far:
> 
> - kernel cmdline is limited resource and large machines tend to have many
>     memory ranges that may excceed kernel cmdline limit size.
> - kASLR doesn't work with memmap=exactmap, because kASLR happens early than
>     user defined memmap=exactmap takes effect.
> 
> Unfortunately, saved_max_pfn still got its user out there (calgry pci, it looks
> like the only one). So for backward compatibility, I'm introducing a new option
> --pass-memmap-cmdline to force kexec-tools to pass memmap=exactmap, the old way.
> 
> This patchset contains massive updates from the previous one. I take some
> suggestions from reviewers. I try to split the changes into smaller pieces and
> keep the whole change as minimal as I can so it wouldn't be too harsh to review
> the patch.
> 
> Any comment is appreciate!
> 
> v7->v6:
> dyoung/Simon:
>  - more description for CRASH_MAX_MEMMAP_NR to be 1024

Hi, Simon

I've changed 5/9 regarding Dave's comment and yours. Could you please
pick up this patchset if there's no more problem?

Thanks
WANG Chao

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

  parent reply	other threads:[~2014-04-22  4:38 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 ` WANG Chao [this message]
2014-04-23  0:14   ` [PATCH v7 0/9] kexec-tools, x86: E820 memmap pass " Simon Horman
2014-04-23  3:31     ` WANG Chao
2014-05-07 14:45 ` Vivek Goyal
2014-05-08 11:31   ` 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=20140422043751.GD4564@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