Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan <bhe@redhat.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: Toshi Kani <toshi.kani@hp.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	tangchen@cn.fujitsu.com, linux-acpi@vger.kernel.org,
	zhangyanfei@cn.fujitsu.com, dyoung@redhat.com,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: kdump failed because of hotplug memory adding in kdump kernel
Date: Fri, 10 Jan 2014 17:14:33 +0800	[thread overview]
Message-ID: <20140110091433.GA14074@dhcp-16-105.nay.redhat.com> (raw)
In-Reply-To: <52CFAA20.2010109@jp.fujitsu.com>


 >In ns
> >object tree, they are not treated as hotplug memory.
> 
> wrong.
> They are treated as hotplug memory. But the memory cannot hot removed
> because the memory has kernel memory.
> 
> >Otherwise, any hotplug memory which is not reserved for 2nd kernel can
> >be parsed and need be added as hotplug memory, and add them into movable
> >zone.
> 
> wrong.
> The memory is allocated as normal zone and it is offline.

Hi,

Thanks for answering.

I am confused. Now the fact is in 1st kernel memory is reserved for
crashkernel and passed to 2nd kernel by exactmap. Then in 2nd kernel,
reserved memory regions are added into e820. Later hotplug memory still
trigger add_memory, and cause bug I reported.


> 
> >
> >Am I right?
> >
> 
> >The other question, e820 reserve is done earlier than acpi
> >initialization, because acpi_early_init() invocation is very late in
> >start_kernel(). Does that means at the very beginning all memorys are in
> >e820, later when acpi_early_init is called, hotplug memory is detected,
> >they will be moved to different place or need be marked with a specific
> >flag?
> 
> No.
> 
> Thanks,
> Yasuaki Ishimatsu
> 


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

  reply	other threads:[~2014-01-10  9:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 15:26 kdump failed because of hotplug memory adding in kdump kernel Baoquan
2014-01-08 15:58 ` Vivek Goyal
2014-01-08 23:07   ` Rafael J. Wysocki
2014-01-09  0:11     ` Toshi Kani
2014-01-09 13:10       ` Rafael J. Wysocki
2014-01-09 14:53         ` Vivek Goyal
2014-01-09 16:15           ` Toshi Kani
2014-01-09 14:50       ` Vivek Goyal
2014-01-09 16:03         ` Toshi Kani
2014-01-09 16:24           ` Vivek Goyal
2014-01-09 17:24             ` Toshi Kani
2014-01-09 18:23               ` Vivek Goyal
2014-01-09 18:34                 ` Toshi Kani
2014-01-09 21:27                   ` Vivek Goyal
2014-01-09 21:56                     ` Toshi Kani
2014-01-10  7:11                       ` Baoquan
2014-01-10  8:06                         ` Yasuaki Ishimatsu
2014-01-10  9:14                           ` Baoquan [this message]
2014-01-10  9:35                             ` Yasuaki Ishimatsu
2014-01-10 10:27                               ` Baoquan
2014-01-10 15:19                             ` Toshi Kani
2014-01-10 15:56                         ` Toshi Kani
2014-01-10  1:40                   ` Rafael J. Wysocki
2014-01-09  3:22     ` Baoquan
2014-01-09 14:48     ` 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=20140110091433.GA14074@dhcp-16-105.nay.redhat.com \
    --to=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tangchen@cn.fujitsu.com \
    --cc=toshi.kani@hp.com \
    --cc=vgoyal@redhat.com \
    --cc=zhangyanfei@cn.fujitsu.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