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@xxxxxxxxxx wrote: > From: Jérôme Glisse <jglisse@xxxxxxxxxx> > > 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@xxxxxxxxxx> > Cc: Guenter Roeck <linux@xxxxxxxxxxxx> > Cc: Leon Romanovsky <leonro@xxxxxxxxxxxx> > Cc: Jason Gunthorpe <jgg@xxxxxxxxxxxx> > Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: Ralph Campbell <rcampbell@xxxxxxxxxx> > Cc: John Hubbard <jhubbard@xxxxxxxxxx> > --- > 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 >
