On Mon 28-01-13 09:33:49, Tang Chen wrote: > On 01/25/2013 09:17 PM, Michal Hocko wrote: > >On Wed 23-01-13 06:29:31, Simon Jeons wrote: > >>On Tue, 2013-01-22 at 19:42 +0800, Tang Chen wrote: > >>>Here are some bug fix patches for physical memory hot-remove. All these > >>>patches are based on the latest -mm tree. > >>>git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm > >>> > >>>And patch1 and patch3 are very important. > >>>patch1: free compound pages when freeing memmap, otherwise the kernel > >>> will panic the next time memory is hot-added. > >>>patch3: the old way of freeing pagetable pages was wrong. We should never > >>> split larger pages into small ones. > >>> > >>> > >> > >>Hi Tang, > >> > >>I remember your big physical memory hot-remove patchset has already > >>merged by Andrew, but where I can find it? Could you give me git tree > >>address? > > > >Andrew tree is also mirrored into a git tree. > >http://git.kernel.org/?p=linux/kernel/git/mhocko/mm.git;a=summary > > > >It contains only Memory management patches on top of the last major > >release (since-.X.Y branch). > > Hi Michal, > > I'm not sure I got your meaning. :) Well, the mirror tree gets updated when Andrew releases mmotm and quite often even when mmots is released. All patches in the mm section are applied. > In http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git akpm, > I can find the following commit. > > commit deed0460e01b3968f2cf46fb94851936535b7e0d > Author: Tang Chen <tangchen@xxxxxxxxxxxxxx> > Date: Sat Jan 19 11:07:13 2013 +1100 > > memory-hotplug: do not allocate pgdat if it was not freed when > offline. > > > This is one of memory hot-remove patches. Please try to update the > mirror tree, > and try to find the above commit. That one is in my mirror tree as f48bf999 (memory-hotplug: do not allocate pdgat if it was not freed when offline.). -- Michal Hocko SUSE Labs -- 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