From: John Hubbard <jhubbard@nvidia.com>
To: Oliver O'Halloran <oohall@gmail.com>, <linuxppc-dev@lists.ozlabs.org>
Cc: <bsingharora@gmail.com>, <linux-mm@kvack.org>
Subject: Re: [PATCH v3 1/6] mm, x86: Add ARCH_HAS_ZONE_DEVICE to Kconfig
Date: Fri, 23 Jun 2017 20:26:37 -0700 [thread overview]
Message-ID: <ce32f815-24db-4656-78e2-df3af37da2bb@nvidia.com> (raw)
In-Reply-To: <20170623083122.5992-1-oohall@gmail.com>
On 06/23/2017 01:31 AM, Oliver O'Halloran wrote:
> Currently ZONE_DEVICE depends on X86_64 and this will get unwieldly as
> new architectures (and platforms) get ZONE_DEVICE support. Move to an
> arch selected Kconfig option to save us the trouble.
>
> Cc: linux-mm@kvack.org
> Acked-by: Ingo Molnar <mingo@kernel.org>
> Acked-by: Balbir Singh <bsingharora@gmail.com>
> Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
> ---
> v2: Added missing hunk.
> v3: No changes
> ---
> arch/x86/Kconfig | 1 +
> mm/Kconfig | 6 +++++-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 0efb4c9497bc..325429a3f32f 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -59,6 +59,7 @@ config X86
> select ARCH_HAS_STRICT_KERNEL_RWX
> select ARCH_HAS_STRICT_MODULE_RWX
> select ARCH_HAS_UBSAN_SANITIZE_ALL
> + select ARCH_HAS_ZONE_DEVICE if X86_64
> select ARCH_HAVE_NMI_SAFE_CMPXCHG
> select ARCH_MIGHT_HAVE_ACPI_PDC if ACPI
> select ARCH_MIGHT_HAVE_PC_PARPORT
> diff --git a/mm/Kconfig b/mm/Kconfig
> index beb7a455915d..790e52a8a486 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -683,12 +683,16 @@ config IDLE_PAGE_TRACKING
>
> See Documentation/vm/idle_page_tracking.txt for more details.
>
> +# arch_add_memory() comprehends device memory
> +config ARCH_HAS_ZONE_DEVICE
> + bool
> +
> config ZONE_DEVICE
> bool "Device memory (pmem, etc...) hotplug support"
> depends on MEMORY_HOTPLUG
> depends on MEMORY_HOTREMOVE
> depends on SPARSEMEM_VMEMMAP
> - depends on X86_64 #arch_add_memory() comprehends device memory
> + depends on ARCH_HAS_ZONE_DEVICE
>
> help
> Device memory hotplug support allows for establishing pmem,
>
Hi Oliver,
+1, this is nice to have, and it behaves as expected on x86_64 with and without HMM, at
least with the small bit of Kconfig dependency testing I did here.
thanks,
john h
prev parent reply other threads:[~2017-06-24 3:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 8:31 [PATCH v3 1/6] mm, x86: Add ARCH_HAS_ZONE_DEVICE to Kconfig Oliver O'Halloran
2017-06-23 8:31 ` [PATCH v3 2/6] powerpc/vmemmap: Reshuffle vmemmap_free() Oliver O'Halloran
2017-06-26 2:46 ` Balbir Singh
2017-06-23 8:31 ` [PATCH v3 3/6] powerpc/vmemmap: Add altmap support Oliver O'Halloran
2017-06-23 8:31 ` [PATCH v3 4/6] powerpc/mm: Add devmap support for ppc64 Oliver O'Halloran
2017-06-25 5:16 ` kbuild test robot
2017-06-27 2:33 ` Michael Ellerman
2017-06-27 8:24 ` Oliver
2017-06-23 8:31 ` [PATCH v3 5/6] powerpc/mm: Wire up hpte_removebolted for powernv Oliver O'Halloran
2017-06-23 8:31 ` [PATCH v3 6/6] powerpc/mm: Enable ZONE_DEVICE on powerpc Oliver O'Halloran
2017-06-24 3:26 ` John Hubbard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce32f815-24db-4656-78e2-df3af37da2bb@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).