android_kernel_xiaomi_sm8350/arch/ia64/mm
Dave Hansen 208d54e551 [PATCH] memory hotplug locking: node_size_lock
pgdat->node_size_lock is basically only neeeded in one place in the normal
code: show_mem(), which is the arch-specific sysrq-m printing function.

Strictly speaking, the architectures not doing memory hotplug do no need this
locking in show_mem().  However, they are all included for completeness.  This
should also make any future consolidation of all of the implementations a
little more straightforward.

This lock is also held in the sparsemem code during a memory removal, as
sections are invalidated.  This is the place there pfn_valid() is made false
for a memory area that's being removed.  The lock is only required when doing
pfn_valid() operations on memory which the user does not already have a
reference on the page, such as in show_mem().

Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-29 21:40:44 -07:00
..
contig.c [PATCH] V5 ia64 SPARSEMEM - eliminate contig_page_data 2005-10-04 13:20:23 -07:00
discontig.c [PATCH] memory hotplug locking: node_size_lock 2005-10-29 21:40:44 -07:00
extable.c Linux-2.6.12-rc2 2005-04-16 15:20:36 -07:00
fault.c [PATCH] mm: ia64 use expand_upwards 2005-10-29 21:40:39 -07:00
hugetlbpage.c [IA64] Rationalise Region Definitions 2005-08-24 15:35:41 -07:00
init.c [PATCH] mm: init_mm without ptlock 2005-10-29 21:40:40 -07:00
Makefile [PATCH] V5 ia64 SPARSEMEM - Kconfig and Makefile 2005-10-04 13:19:30 -07:00
numa.c [PATCH] V5 ia64 SPARSEMEM - SPARSEMEM code changes 2005-10-04 13:21:38 -07:00
tlb.c [PATCH] mm: flush_tlb_range outside ptlock 2005-10-29 21:40:40 -07:00