From: Jerome Glisse <jglisse@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Leon Romanovsky <leonro@mellanox.com>,
Jason Gunthorpe <jgg@mellanox.com>,
Ralph Campbell <rcampbell@nvidia.com>,
linux-mm@kvack.org, John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH] mm/hmm: add ARCH_HAS_HMM_MIRROR ARCH_HAS_HMM_DEVICE Kconfig
Date: Wed, 1 May 2019 14:38:51 -0400 [thread overview]
Message-ID: <20190501183850.GA4018@redhat.com> (raw)
In-Reply-To: <20190417211141.17580-1-jglisse@redhat.com>
Andrew just the patch that would be nice to get in 5.2 so i can fix
device driver Kconfig before doing the real update to mm HMM Kconfig
On Wed, Apr 17, 2019 at 05:11:41PM -0400, jglisse@redhat.com wrote:
> From: Jérôme Glisse <jglisse@redhat.com>
>
> This patch just add 2 new Kconfig that are _not use_ by anyone. I check
> that various make ARCH=somearch allmodconfig do work and do not complain.
> This new Kconfig need to be added first so that device driver that do
> depend on HMM can be updated.
>
> Once drivers are updated then i can update the HMM Kconfig to depends
> on this new Kconfig in a followup patch.
>
> Signed-off-by: Jérôme Glisse <jglisse@redhat.com>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Leon Romanovsky <leonro@mellanox.com>
> Cc: Jason Gunthorpe <jgg@mellanox.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ralph Campbell <rcampbell@nvidia.com>
> Cc: John Hubbard <jhubbard@nvidia.com>
> ---
> mm/Kconfig | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index 25c71eb8a7db..daadc9131087 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -676,6 +676,22 @@ config ZONE_DEVICE
>
> If FS_DAX is enabled, then say Y.
>
> +config ARCH_HAS_HMM_MIRROR
> + bool
> + default y
> + depends on (X86_64 || PPC64)
> + depends on MMU && 64BIT
> +
> +config ARCH_HAS_HMM_DEVICE
> + bool
> + default y
> + depends on (X86_64 || PPC64)
> + depends on MEMORY_HOTPLUG
> + depends on MEMORY_HOTREMOVE
> + depends on SPARSEMEM_VMEMMAP
> + depends on ARCH_HAS_ZONE_DEVICE
> + select XARRAY_MULTI
> +
> config ARCH_HAS_HMM
> bool
> default y
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-05-01 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 21:11 [PATCH] mm/hmm: add ARCH_HAS_HMM_MIRROR ARCH_HAS_HMM_DEVICE Kconfig jglisse
2019-05-01 18:38 ` Jerome Glisse [this message]
2019-05-01 19:23 ` Guenter Roeck
2019-05-02 16:22 ` Jerome Glisse
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=20190501183850.GA4018@redhat.com \
--to=jglisse@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@mellanox.com \
--cc=jhubbard@nvidia.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=rcampbell@nvidia.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).