Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Chao <chaowang@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org, Linn Crosetto <linn@hp.com>,
	hpa@zytor.com, dyoung@redhat.com, trenn@suse.de,
	vgoyal@redhat.com, ebiederm@xmission.com
Subject: Re: [PATCH v4 0/4] kexec-tools, x86: E820 memmap pass for kdump
Date: Thu, 20 Mar 2014 13:00:49 +0800	[thread overview]
Message-ID: <20140320050049.GE24486@dhcp-17-89.nay.redhat.com> (raw)
In-Reply-To: <20140320035012.GC10601@verge.net.au>

On 03/20/14 at 12:50pm, Simon Horman wrote:
> On Wed, Mar 19, 2014 at 11:57:57AM -0600, Linn Crosetto wrote:
> > On Wed, Mar 19, 2014 at 04:03:57PM +0800, WANG Chao wrote:
> > > Hi, All
> > > 
> > > When kaslr comes in and kdump is broken, it seems about the right time to use
> > > E820 instead of memmap=exactmap to pass memmap for kdump for the default memmap
> > > passing mechanism:
> > > http://lists.infradead.org/pipermail/kexec/2014-February/011048.html
> > > 
> > > 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.
> > > 
> > > Any comment is appreciate!
> > > 
> > > v3->v4:
> > > Linn: check return value of malloc (use xmalloc)
> > > me: fix dbgprintf_mem_range
> > > 
> > > v2->v3:
> > > Linn:
> > >  - do not free sd (setup_data) buffer
> > >  - reuse code in setup_e820 and setup_e820_ext
> > > 
> > > v1->v2:
> > > 
> > > Vivek:
> > >  - Use function instead of macro for dbgprint_mem_range
> > >  - Do not pass reserved memory range for kdump. It could addressed later
> > >    separately.
> > > 
> > > WANG Chao (4):
> > >   cleanup: add dbgprint_mem_range function
> > >   x86: Store memory ranges globally used for crash kernel to boot into
> > >   x86: add --pass-memmap-cmdline option
> > >   x86: Pass memory range via E820 for kdump
> > > 
> > >  kexec/arch/i386/crashdump-x86.c        | 157 ++++++++++++++++--------------
> > >  kexec/arch/i386/crashdump-x86.h        |   6 +-
> > >  kexec/arch/i386/include/arch/options.h |   2 +
> > >  kexec/arch/i386/kexec-x86-common.c     |   6 +-
> > >  kexec/arch/i386/kexec-x86.c            |   4 +
> > >  kexec/arch/i386/kexec-x86.h            |   1 +
> > >  kexec/arch/i386/x86-linux-setup.c      | 171 ++++++++++++++++++++++-----------
> > >  kexec/arch/i386/x86-linux-setup.h      |   1 +
> > >  kexec/arch/x86_64/kexec-x86_64.c       |   5 +
> > >  kexec/kexec.c                          |  10 ++
> > >  kexec/kexec.h                          |   1 +
> > >  11 files changed, 231 insertions(+), 133 deletions(-)
> > 
> > Thanks for the patches. Tested (adding a fix provided by Dave Young for
> > http://lists.infradead.org/pipermail/kexec/2014-March/011262.html) and
> > successful with both kexec and kdump, both with and without
> > --pass-memmap-cmdline.
> 

Hi, Simon. I'll answer the questions below.

> Is the patch a pre-requisite for this series?

No. That's a separate problem of EFI. Old kexec-tools also needs the
patch.

> If so, has it been posted formally?

Dave Young has sent to patch to kexec mail list. The subject is as
follow:

[PATCH] kexec-tools: handle 64bit efi memmap address correctly

> If so, could you point it out to me?

Dave's patch:
http://lists.infradead.org/pipermail/kexec/2014-March/011303.html

Thanks
WANG Chao

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

  reply	other threads:[~2014-03-20  5:01 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  8:03 [PATCH v4 0/4] kexec-tools, x86: E820 memmap pass for kdump WANG Chao
2014-03-19  8:03 ` [PATCH v4 1/4] cleanup: add dbgprint_mem_range function WANG Chao
2014-03-20  3:49   ` Simon Horman
2014-03-19  8:03 ` [PATCH v4 2/4] x86: Store memory ranges globally used for crash kernel to boot into WANG Chao
2014-03-27 22:32   ` Vivek Goyal
2014-03-28  5:23     ` WANG Chao
2014-03-28 14:01       ` Vivek Goyal
2014-03-28 15:44       ` Thomas Renninger
2014-03-28 16:05         ` Vivek Goyal
2014-03-28  2:19   ` Dave Young
2014-03-28  5:36     ` WANG Chao
2014-03-28  3:24   ` Dave Young
2014-03-28  6:13     ` WANG Chao
2014-03-28  6:43       ` Dave Young
2014-03-28  6:51         ` Dave Young
2014-03-28  7:12           ` Dave Young
2014-04-01  7:04         ` WANG Chao
2014-04-01  8:41           ` Dave Young
2014-04-01  8:54             ` WANG Chao
2014-04-01  9:36               ` Dave Young
2014-04-01  9:52                 ` WANG Chao
2014-03-19  8:04 ` [PATCH v4 3/4] x86: add --pass-memmap-cmdline option WANG Chao
2014-03-19  8:04 ` [PATCH v4 4/4] x86: Pass memory range via E820 for kdump WANG Chao
2014-03-27 22:50   ` Vivek Goyal
2014-03-28  4:52     ` WANG Chao
2014-03-28 13:53       ` Vivek Goyal
2014-03-28  3:28   ` Dave Young
2014-03-28  4:53     ` WANG Chao
2014-03-19 17:57 ` [PATCH v4 0/4] kexec-tools, x86: E820 memmap pass " Linn Crosetto
2014-03-20  3:50   ` Simon Horman
2014-03-20  5:00     ` WANG Chao [this message]
2014-03-20 15:42 ` Vivek Goyal
2014-03-27 10:31   ` WANG Chao
2014-03-27 22:23     ` Vivek Goyal

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=20140320050049.GE24486@dhcp-17-89.nay.redhat.com \
    --to=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=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