* Can switching to FLATMEM cause bugs?
@ 2013-06-10 9:13 Jani Monoses
0 siblings, 0 replies; only message in thread
From: Jani Monoses @ 2013-06-10 9:13 UTC (permalink / raw)
To: linux-arm-kernel
Hello,
enabling memory control groups in a Nexus 4 kernel causes boot hangs due
to what I think is a mismatch between where the cgroup code looks for
memory blocks to account for and physical memory layout of the Nexus 4
platform. It skips two blocks which are not aligned to 64K which is the
increment used by memcg initialization code. When later there are
references to pages in one of these blocks, there's a page fault due to
invalid cgroup block links.
I found a workaround to be switching to FLATMEM from SPARSEMEM. Could
this switch cause bugs by itself? I am not sure whether a certain choice
of memory model is only about best resource utilization and performance
or it has implications on the correctness of the memory manager.
thanks
Jani
PS: The details of what I think is the bug on the cgroup mailing list
http://permalink.gmane.org/gmane.linux.kernel.cgroups/7003
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-06-10 9:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-10 9:13 Can switching to FLATMEM cause bugs? Jani Monoses
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).