lkml.org 
[lkml]   [2014]   [Oct]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v2 0/4] Low/high memory CMA reservation fixes
Date
Hello,

This patch set fixes an issue introduced by commits 95b0e655f914 ("ARM: mm:
don't limit default CMA region only to low memory") and f7426b983a6a ("mm:
cma: adjust address limit to avoid hitting low/high memory boundary")
resulting in reserved areas crossing the low/high memory boundary.

Patches 1/4 and 2/4 fix sides issues, with the bulk of the work in patch 3/4.
Patch 4/4 then fixes a printk issue that got me puzzled wondering why memory
reported under the lowmem limit was actually highmem.

This series fixes a v3.18-rc1 regression causing Renesas Koelsch boot
breakages when CMA is enabled.

Changes since v1:

- Use the cma count field to detect non-activated reservations
- Remove the redundant limit adjustment

Laurent Pinchart (4):
mm: cma: Don't crash on allocation if CMA area can't be activated
mm: cma: Always consider a 0 base address reservation as dynamic
mm: cma: Ensure that reservations never cross the low/high mem
boundary
mm: cma: Use %pa to print physical addresses

mm/cma.c | 68 +++++++++++++++++++++++++++++++++++++++++-----------------------
1 file changed, 44 insertions(+), 24 deletions(-)

--
Regards,

Laurent Pinchart



\
 
 \ /
  Last update: 2014-10-24 13:01    [W:0.089 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site