Re: [PATCH v4, part3 11/15] mm: use a dedicated lock to protect totalram_pages and zone->managed_pages

2013-04-08 Thread Jiang Liu
On 04/08/2013 09:39 PM, Rik van Riel wrote: > On 04/06/2013 09:55 AM, Jiang Liu wrote: > >> @@ -5186,6 +5189,22 @@ early_param("movablecore", cmdline_parse_movablecore); >> >> #endif /* CONFIG_HAVE_MEMBLOCK_NODE_MAP */ >> >> +void adjust_managed_page_count(struct page *page, long count) >> +{ >>

Re: [PATCH v4, part3 11/15] mm: use a dedicated lock to protect totalram_pages and zone->managed_pages

2013-04-08 Thread Rik van Riel
On 04/06/2013 09:55 AM, Jiang Liu wrote: @@ -5186,6 +5189,22 @@ early_param("movablecore", cmdline_parse_movablecore); #endif /* CONFIG_HAVE_MEMBLOCK_NODE_MAP */ +void adjust_managed_page_count(struct page *page, long count) +{ + bool lock = (system_state != SYSTEM_BOOTING); + +

[PATCH v4, part3 11/15] mm: use a dedicated lock to protect totalram_pages and zone->managed_pages

2013-04-06 Thread Jiang Liu
Currently lock_memory_hotplug()/unlock_memory_hotplug() are used to protect totalram_pages and zone->managed_pages. Other than the memory hotplug driver, totalram_pages and zone->managed_pages may also be modified at runtime by other drivers, such as Xen balloon, virtio_balloon etc. For those cases