[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <43610D35-58EE-4019-B979-EAE3F4781EAA@kernel.org>
Date: Tue, 15 Oct 2019 08:42:07 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: Adam Ford <aford173@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Christoph Hellwig <hch@....de>,
Fabio Estevam <festevam@...il.com>,
Lucas Stach <l.stach@...gutronix.de>,
etnaviv@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Mike Rapoport <rppt@...ux.ibm.com>
Subject: Re: [PATCH] mm: memblock: do not enforce current limit for memblock_phys* family
On October 15, 2019 12:44:23 AM GMT+02:00, Andrew Morton <akpm@...ux-foundation.org> wrote:
>On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport <rppt@...nel.org>
>wrote:
>
>> Until commit 92d12f9544b7 ("memblock: refactor internal allocation
>> functions") the maximal address for memblock allocations was forced
>to
>> memblock.current_limit only for the allocation functions returning
>virtual
>> address. The changes introduced by that commit moved the limit
>enforcement
>> into the allocation core and as a result the allocation functions
>returning
>> physical address also started to limit allocations to
>> memblock.current_limit.
>>
>> This caused breakage of etnaviv GPU driver:
>>
>> ...
>>
>
>So I'll add a cc:stable, yes?
Yeah, right. Somehow I've missed that...
--
Sincerely yours,
Mike
Powered by blists - more mailing lists