[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0u4tN+mIgNSWwdi@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
Date: Sun, 16 Oct 2022 09:54:28 +0200
From: Alexander Gordeev <agordeev@...ux.ibm.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Christophe Leroy <christophe.leroy@...roup.eu>,
Baoquan He <bhe@...hat.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Linux-Arch <linux-arch@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@...radead.org>,
wangkefeng.wang@...wei.com, schnelle@...ux.ibm.com,
David.Laight@...lab.com, shorne@...il.com
Subject: Re: [RFC PATCH 7/8] mm/ioremap: Consider IOREMAP space in generic
ioremap
On Wed, Oct 12, 2022 at 12:39:11PM +0200, Arnd Bergmann wrote:
> "Some" means exactly powerpc64, right? It looks like microblaze
> and powerpc32 still share some of this code, but effectively
> just use the vmalloc area once the slab allocator is up.
>
> Is the special case still useful for powerpc64 or could this be
> changed to do it the same as everything else?
Or make it the other way around and set IOREMAP_START/IOREMAP_END
to VMALLOC_START/VMALLOC_END by default?
>
> Arnd
Powered by blists - more mailing lists