From mboxrd@z Thu Jan 1 00:00:00 1970 From: iamjoonsoo.kim@lge.com (Joonsoo Kim) Date: Mon, 27 Oct 2014 16:44:42 +0900 Subject: [PATCH v2 3/4] mm: cma: Ensure that reservations never cross the low/high mem boundary In-Reply-To: <1436531.s0VJY8ZaKv@avalon> References: <1414145922-26042-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com> <1414145922-26042-4-git-send-email-laurent.pinchart+renesas@ideasonboard.com> <1436531.s0VJY8ZaKv@avalon> Message-ID: <20141027074442.GD23379@js1304-P5Q-DELUXE> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 > > > > > > > Acked-by: Michal Nazarewicz > > Thank you. Can we get this series merged in v3.18-rc ? Hello, You'd better to resend whole series to Andrew. Thanks.