[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191127085351.GA24676@lst.de>
Date: Wed, 27 Nov 2019 09:53:51 +0100
From: Christoph Hellwig <hch@....de>
To: Mike Rapoport <rppt@...ux.ibm.com>
Cc: Christoph Hellwig <hch@....de>,
Christian Zigotzky <chzigotzky@...osoft.de>,
Robin Murphy <robin.murphy@....com>,
linux-arch@...r.kernel.org, darren@...vens-zone.net,
mad skateman <madskateman@...il.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
iommu@...ts.linux-foundation.org, Rob Herring <robh+dt@...nel.org>,
paulus@...ba.org, rtd2@...a.co.nz,
"contact@...on.com" <contact@...on.com>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
nsaenzjulienne@...e.de
Subject: Re: Bug 205201 - Booting halts if Dawicontrol DC-2976 UW SCSI
board installed, unless RAM size limited to 3500M
On Wed, Nov 27, 2019 at 08:56:25AM +0200, Mike Rapoport wrote:
> Maybe we'll simply force bottom up allocation before calling
> swiotlb_init()? Anyway, it's the last memblock allocation.
That should work, but I don't think it is the proper fix. The underlying
issue here is that ZONE_DMA/DMA32 sizing is something that needs to
be propagated to memblock and dma-direct as is based around addressing
limitations. But our zone initialization is such a mess that we
can't just reuse a variable. Nicolas has started to clean some of
this up, but we need to clean that whole zone initialization mess up
a lot more.
Powered by blists - more mailing lists