lkml.org 
[lkml]   [2014]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 3/4] mm: cma: Ensure that reservations never cross the low/high mem boundary
On Sun, Oct 26, 2014 at 02:43:52PM +0200, Laurent Pinchart wrote:
> On Friday 24 October 2014 18:26:58 Michal Nazarewicz wrote:
> > On Fri, Oct 24 2014, Laurent Pinchart wrote:
> > > Commit 95b0e655f914 ("ARM: mm: don't limit default CMA region only to
> > > low memory") extended CMA memory reservation to allow usage of high
> > > memory. It relied on commit f7426b983a6a ("mm: cma: adjust address limit
> > > to avoid hitting low/high memory boundary") to ensure that the reserved
> > > block never crossed the low/high memory boundary. While the
> > > implementation correctly lowered the limit, it failed to consider the
> > > case where the base..limit range crossed the low/high memory boundary
> > > with enough space on each side to reserve the requested size on either
> > > low or high memory.
> > >
> > > Rework the base and limit adjustment to fix the problem. The function
> > > now starts by rejecting the reservation altogether for fixed
> > > reservations that cross the boundary, tries to reserve from high memory
> > > first and then falls back to low memory.
> > >
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> >
> > Acked-by: Michal Nazarewicz <mina86@mina86.com>
>
> Thank you. Can we get this series merged in v3.18-rc ?


Hello,

You'd better to resend whole series to Andrew.

Thanks.


\
 
 \ /
  Last update: 2014-10-27 09:21    [W:0.052 / U:1.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site