android_kernel_xiaomi_sm8350/arch/x86_64
Zou Nan hai 2e1c49db4c x86_64: allocate sparsemem memmap above 4G
On systems with huge amount of physical memory, VFS cache and memory memmap
may eat all available system memory under 4G, then the system may fail to
allocate swiotlb bounce buffer.

There was a fix for this issue in arch/x86_64/mm/numa.c, but that fix dose
not cover sparsemem model.

This patch add fix to sparsemem model by first try to allocate memmap above
4G.

Signed-off-by: Zou Nan hai <nanhai.zou@intel.com>
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Andi Kleen <ak@suse.de>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-06-01 08:18:27 -07:00
..
boot [PATCH] x86-64: Share identical video.S between i386 and x86-64 2007-05-02 19:27:21 +02:00
crypto
ia32 Detach sched.h from mm.h 2007-05-21 09:18:19 -07:00
kernel Avoid zero size allocation in cache_k8_northbridges() 2007-05-23 20:14:12 -07:00
lib
mm x86_64: allocate sparsemem memmap above 4G 2007-06-01 08:18:27 -07:00
oprofile
pci
defconfig x86_64: Update defconfig 2007-05-21 09:56:56 -07:00
Kconfig i386, x86-64: show that CONFIG_HOTPLUG_CPU is required for suspend on SMP 2007-05-23 20:14:14 -07:00
Kconfig.debug
Makefile [PATCH] x86-64: Remove CONFIG_REORDER 2007-05-02 19:27:21 +02:00