On 01/10/14 at 06:35pm, Yasuaki Ishimatsu wrote: > (2014/01/10 18:14), Baoquan wrote: > > > > >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. > > Does the issue occur even if you apply the following Prarit's patch to > your kernel and add no_memory_hotplug boot option to 2nd kernel? > > http://marc.info/?l=linux-acpi&m=138922019607796&w=2 This issue is the same as Prarit's. He posted the formal patch. But still there are some questions we want to know. > > Thanks, > Yasuaki Ishimatsu > > > > > > >> > >>> > >>>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 > >> > > > >-- > >To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > >the body of a message to majordomo at vger.kernel.org > >More majordomo info at http://vger.kernel.org/majordomo-info.html > > > >
