[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d0acd053-96d3-4e18-a9de-97987d8be14b@app.fastmail.com>
Date: Wed, 12 Oct 2022 12:39:11 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Christophe Leroy" <christophe.leroy@...roup.eu>,
"Baoquan He" <bhe@...hat.com>
Cc: 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>, agordeev@...ux.ibm.com,
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:09 PM, Christophe Leroy wrote:
> Some architecture have a dedicated space for IOREMAP mappings.
>
> If so, use it in generic_ioremap_pro().
>
> Signed-off-by: Christophe Leroy <christophe.leroy@...roup.eu>
"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?
Arnd
Powered by blists - more mailing lists