[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190902130101.GA2051@lst.de>
Date: Mon, 2 Sep 2019 15:01:01 +0200
From: Christoph Hellwig <hch@....de>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: Catalin Marinas <catalin.marinas@....com>,
Christoph Hellwig <hch@....de>, linux-mm@...ck.org,
linux-riscv@...ts.infradead.org, will@...nel.org,
m.szyprowski@...sung.com, linux-arch@...r.kernel.org,
f.fainelli@...il.com, frowand.list@...il.com,
devicetree@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
marc.zyngier@....com, robh+dt@...nel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, phill@...pberryi.org,
mbrugger@...e.com, eric@...olt.net, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, wahrenst@....net,
akpm@...ux-foundation.org, Robin Murphy <robin.murphy@....com>
Subject: Re: [PATCH v2 01/11] asm-generic: add dma_zone_size
On Fri, Aug 30, 2019 at 07:24:25PM +0200, Nicolas Saenz Julienne wrote:
> I'll be happy to implement it that way. I agree it's a good compromise.
>
> @Christoph, do you still want the patch where I create 'zone_dma_bits'? With a
> hardcoded ZONE_DMA it's not absolutely necessary. Though I remember you said it
> was a first step towards being able to initialize dma-direct's min_mask in
> meminit.
I do like the variable better than the current #define. I wonder if
really want a mask or a max_zone_dma_address like variable. So for this
series feel free to drop the patch. I'll see if I'll pick it up
later or if we can find some way to automatically propagate that
information from the zone initialization.
Powered by blists - more mailing lists