[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4heZ7+2QuS2YXYsZcU9EOb87MDymfO8-+bLhbPgYQAYJw@mail.gmail.com>
Date: Fri, 12 Apr 2019 12:37:16 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Robin Murphy <robin.murphy@....com>
Cc: Linux MM <linux-mm@...ck.org>, "Weiny, Ira" <ira.weiny@...el.com>,
Jérôme Glisse <jglisse@...hat.com>,
"Oliver O'Halloran" <oohall@...il.com>, X86 ML <x86@...nel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND 3/3] mm: introduce ARCH_HAS_PTE_DEVMAP
On Fri, Apr 12, 2019 at 12:02 PM Robin Murphy <robin.murphy@....com> wrote:
>
> ARCH_HAS_ZONE_DEVICE is somewhat meaningless in itself, and combined
> with the long-out-of-date comment can lead to the impression than an
> architecture may just enable it (since __add_pages() now "comprehends
> device memory" for itself) and expect things to work.
>
> In practice, however, ZONE_DEVICE users have little chance of
> functioning correctly without __HAVE_ARCH_PTE_DEVMAP, so let's clean
> that up the same way as ARCH_HAS_PTE_SPECIAL and make it the proper
> dependency so the real situation is clearer.
Looks good to me.
Acked-by: Dan Williams <dan.j.williams@...el.com>
Powered by blists - more mailing lists