On Tue, 2014-01-14 at 11:43 +0900, Yasuaki Ishimatsu wrote: > (2014/01/14 10:41), Toshi Kani wrote: > > On Tue, 2014-01-14 at 10:11 +0900, Yasuaki Ishimatsu wrote: > > : > >>>> I think we need a knob manually enable mem-hotplug when specify memmap. But > >>>> it is another story. > >>>> > >>>> Acked-by: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> > >>> > >>> As mentioned, self-NAK. I have seen a system that I needed to specify > >>> memmap=exactmap & had hotplug memory. I will only keep the acpi_no_memhotplug > >>> option in the next version of the patch. > >> > >> > >> Your following first patch is simply and makes sense. > >> > >> http://marc.info/?l=linux-acpi&m=138922019607796&w=2 > >> > > > > In this option, it also requires changing kexec-tools to specify the new > > option for kdump. It won't be simpler. > > Hmm. > I use memm= boot option and hotplug memory for memory hot-remove. > At least, the patch cannot be accepted. Do you mean mem=nG option? I am curious to know how memory hot-remove works in this case. Don't acpi_memhotplug add all the memory ranges at boot, and defeat the mem=nG option? Thanks, -Toshi -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
