Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	etnaviv@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Fabio Estevam <festevam@gmail.com>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Adam Ford <aford173@gmail.com>, Christoph Hellwig <hch@lst.de>,
	linux-arm-kernel@lists.infradead.org,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH] mm: memblock: do not enforce current limit for memblock_phys* family
Date: Tue, 15 Oct 2019 08:42:07 +0200
Message-ID: <43610D35-58EE-4019-B979-EAE3F4781EAA@kernel.org> (raw)
In-Reply-To: <20191014154423.a472315834ce6a730ccbaf3f@linux-foundation.org>

On October 15, 2019 12:44:23 AM GMT+02:00, Andrew Morton <akpm@linux-foundation.org> wrote:
>On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport <rppt@kernel.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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 21:31 Mike Rapoport
2019-10-14 22:44 ` Andrew Morton
2019-10-15  6:42   ` Mike Rapoport [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43610D35-58EE-4019-B979-EAE3F4781EAA@kernel.org \
    --to=rppt@kernel.org \
    --cc=aford173@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=hch@lst.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-ARM-Kernel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/0 linux-arm-kernel/git/0.git
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/1 linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ https://lore.kernel.org/linux-arm-kernel \
		linux-arm-kernel@lists.infradead.org
	public-inbox-index linux-arm-kernel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-arm-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git