[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210123180911.aafa8404a3a7a30779713456@linux-foundation.org>
Date: Sat, 23 Jan 2021 18:09:11 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Thiago Jung Bauermann <bauerman@...ux.ibm.com>
Cc: rppt@...nel.org, guro@...com, iamjoonsoo.kim@....com,
Ram Pai <linuxram@...ibm.com>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Satheesh Rajendran <sathnaga@...ux.vnet.ibm.com>,
kernel-team@...com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
mhocko@...nel.org, riel@...riel.com
Subject: Re: [PATCH v2 2/2] memblock: do not start bottom-up allocations
with kernel_end
On Fri, 22 Jan 2021 01:37:14 -0300 Thiago Jung Bauermann <bauerman@...ux.ibm.com> wrote:
> Mike Rapoport <rppt@...nel.org> writes:
>
> > > Signed-off-by: Roman Gushchin <guro@...com>
> >
> > Reviewed-by: Mike Rapoport <rppt@...ux.ibm.com>
>
> I've seen a couple of spurious triggers of the WARN_ONCE() removed by this
> patch. This happens on some ppc64le bare metal (powernv) server machines with
> CONFIG_SWIOTLB=y and crashkernel=4G, as described in a candidate patch I posted
> to solve this issue in a different way:
>
> https://lore.kernel.org/linuxppc-dev/20201218062103.76102-1-bauerman@linux.ibm.com/
>
> Since this patch solves that problem, is it possible to include it in the next
> feasible v5.11-rcX, with the following tag?
We could do this, if we're confident that this patch doesn't depend on
[1/2] "mm: cma: allocate cma areas bottom-up"? I think it is...
> Fixes: 8fabc623238e ("powerpc: Ensure that swiotlb buffer is allocated from low memory")
I added that.
Powered by blists - more mailing lists