Files
ubports_kernel_google_msm/include/linux
Benjamin Herrenschmidt e63075a3c9 memblock: Introduce default allocation limit and use it to replace explicit ones
This introduce memblock.current_limit which is used to limit allocations
from memblock_alloc() or memblock_alloc_base(..., MEMBLOCK_ALLOC_ACCESSIBLE).

The old MEMBLOCK_ALLOC_ANYWHERE changes value from 0 to ~(u64)0 and can still
be used with memblock_alloc_base() to allocate really anywhere.

It is -no-longer- cropped to MEMBLOCK_REAL_LIMIT which disappears.

Note to archs: I'm leaving the default limit to MEMBLOCK_ALLOC_ANYWHERE. I
strongly recommend that you ensure that you set an appropriate limit
during boot in order to guarantee that an memblock_alloc() at any time
results in something that is accessible with a simple __va().

The reason is that a subsequent patch will introduce the ability for
the array to resize itself by reallocating itself. The MEMBLOCK core will
honor the current limit when performing those allocations.

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2010-08-05 12:56:07 +10:00
..
2010-07-31 14:20:02 +01:00
2010-05-17 22:39:48 -07:00
2010-05-28 01:38:00 +02:00
2010-06-15 09:56:01 +10:00
2010-05-27 09:12:53 -07:00
2010-05-19 13:38:54 -04:00
2010-06-08 18:44:04 +02:00
2010-05-19 22:41:57 -04:00
2010-05-17 16:30:58 -07:00
2010-05-21 19:30:44 +02:00
2010-05-25 08:07:01 -07:00
2010-05-27 09:12:42 -07:00
2010-05-21 09:34:29 -07:00
2010-05-21 09:37:29 -07:00
2010-05-17 12:17:10 +03:00
2010-06-29 10:38:22 -07:00
2010-07-02 21:59:08 -07:00
2010-05-19 13:44:27 +10:00
2010-05-27 09:12:50 -07:00
2010-05-30 09:02:47 -07:00
2010-05-25 11:41:43 -04:00
2010-05-27 09:12:43 -07:00
2010-05-21 09:34:29 -07:00
2010-05-19 22:40:47 -04:00
2010-08-02 10:37:17 -05:00
2010-05-19 22:15:46 +09:30