search for: sparsemem_vmemmap

...#39;t run into this and other similar issues in the future. The CR4 shadow issue was another recent example issue, also introduced via v4.0 [0]. We can't keep doing this reactively. Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be selected on x86 when: if X86_64 && SPARSEMEM_VMEMMAP Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable distributions to be able to have a single binary kernels and let the rest be figured out, so we can't just disable SPARSEMEM_VMEMMAP for Xen alone, we want to build Xen.. or part of Xen and perhaps keep SPARSEMEM_VMEMMA...

...#39;t run into this and other similar issues in the future. The CR4 shadow issue was another recent example issue, also introduced via v4.0 [0]. We can't keep doing this reactively. Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be selected on x86 when: if X86_64 && SPARSEMEM_VMEMMAP Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable distributions to be able to have a single binary kernels and let the rest be figured out, so we can't just disable SPARSEMEM_VMEMMAP for Xen alone, we want to build Xen.. or part of Xen and perhaps keep SPARSEMEM_VMEMMA...

...he CR4 shadow issue was another >> recent example issue, also introduced via v4.0 [0]. We can't keep >> doing this reactively. >> >> Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be >> selected on x86 when: >> >> if X86_64 && SPARSEMEM_VMEMMAP >> >> Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable > > Why? Again, this is the first I've heard of this as well. FWIW, all > the Xen configs we use have SPARSEMEM_VMEMMAP enabled. Interesting... we have config ARCH_SPARSEMEM_ENABLE depend on...

...he CR4 shadow issue was another >> recent example issue, also introduced via v4.0 [0]. We can't keep >> doing this reactively. >> >> Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be >> selected on x86 when: >> >> if X86_64 && SPARSEMEM_VMEMMAP >> >> Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable > > Why? Again, this is the first I've heard of this as well. FWIW, all > the Xen configs we use have SPARSEMEM_VMEMMAP enabled. Interesting... we have config ARCH_SPARSEMEM_ENABLE depend on...

...her >>> recent example issue, also introduced via v4.0 [0]. We can't keep >>> doing this reactively. >>> >>> Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be >>> selected on x86 when: >>> >>> if X86_64 && SPARSEMEM_VMEMMAP >>> >>> Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable >> >> Why? Again, this is the first I've heard of this as well. FWIW, all >> the Xen configs we use have SPARSEMEM_VMEMMAP enabled. > > Interesting... we have config AR...

...ar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be > selected on x86 when: > > if X86_64 && SPARSEMEM_VMEMMAP > > Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable Why? Again, this is the first I've heard of this as well. FWIW, all the Xen configs we use have SPARSEMEM_VMEMMAP enabled. David > distributions to be able to have a single binary kernels and let the &...

...ar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be > selected on x86 when: > > if X86_64 && SPARSEMEM_VMEMMAP > > Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable Why? Again, this is the first I've heard of this as well. FWIW, all the Xen configs we use have SPARSEMEM_VMEMMAP enabled. David > distributions to be able to have a single binary kernels and let the &...

...n 04.03.15 at 05:53, <JGross at suse.com> wrote: > On 03/03/2015 08:20 PM, Luis R. Rodriguez wrote: >> On Tue, Mar 3, 2015 at 2:06 AM, David Vrabel <david.vrabel at citrix.com> wrote: >>> On 03/03/15 09:40, Luis R. Rodriguez wrote: >>>> if X86_64 && SPARSEMEM_VMEMMAP >>>> >>>> Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable >>> >>> Why? Again, this is the first I've heard of this as well. FWIW, all >>> the Xen configs we use have SPARSEMEM_VMEMMAP enabled. >> >> Inte...

...ar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be > selected on x86 when: > > if X86_64 && SPARSEMEM_VMEMMAP > > Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable > distributions to be able to have a single binary kernels and let the > rest be figured out, so we can't just disable SPARSEMEM_VMEMMAP for > Xen alone, we want to build Xen.. or part of Xen and perh...

...ar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the rabbit hole for a bit. HAVE_ARCH_KASAN will be > selected on x86 when: > > if X86_64 && SPARSEMEM_VMEMMAP > > Now Xen should not have SPARSEMEM_VMEMMAP but PVOPs' goal is to enable > distributions to be able to have a single binary kernels and let the > rest be figured out, so we can't just disable SPARSEMEM_VMEMMAP for > Xen alone, we want to build Xen.. or part of Xen and perh...

...4 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -675,16 +675,6 @@ config ARCH_HAS_HMM_MIRROR 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

...8c8cf4 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -677,13 +677,13 @@ config ARCH_HAS_HMM_MIRROR config ARCH_HAS_HMM bool - default y depends on (X86_64 || PPC64) depends on ZONE_DEVICE depends on MMU && 64BIT depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE depends on SPARSEMEM_VMEMMAP + default y config MIGRATE_VMA_HELPER bool @@ -709,8 +709,7 @@ config HMM_MIRROR config DEVICE_PRIVATE bool "Unaddressable device memory (GPU memory, ...)" - depends on ARCH_HAS_HMM - select HMM + depends on ZONE_DEVICE select DEV_PAGEMAP_OPS help -- 2.20.1

...4 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -675,16 +675,6 @@ config ARCH_HAS_HMM_MIRROR 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

...7a54b3 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -677,13 +677,13 @@ config ARCH_HAS_HMM_MIRROR config ARCH_HAS_HMM bool - default y depends on (X86_64 || PPC64) depends on ZONE_DEVICE depends on MMU && 64BIT depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE depends on SPARSEMEM_VMEMMAP + default y config MIGRATE_VMA_HELPER bool @@ -709,8 +709,7 @@ config HMM_MIRROR config DEVICE_PRIVATE bool "Unaddressable device memory (GPU memory, ...)" - depends on ARCH_HAS_HMM - select HMM + depends on ZONE_DEVICE select DEV_PAGEMAP_OPS help -- 2.20.1

On Fri, May 8, 2020 at 5:00 PM Jason Gunthorpe <jgg at mellanox.com> wrote: > > On Fri, May 08, 2020 at 04:40:09PM +0200, Arnd Bergmann wrote: > > CONFIG_DEVICE_PRIVATE cannot be selected in configurations > > without ZONE_DEVICE: > > It is kind of unfortunate to lift dependencies from DEVICE_PRIVATE > into the users, is this really how kconfig is supposed to work

...nfig ARCH_HAS_HMM_MIRROR - bool - default y - depends on (X86_64 || PPC64) - depends on MMU && 64BIT - -config ARCH_HAS_HMM - bool - depends on (X86_64 || PPC64) - depends on ZONE_DEVICE - depends on MMU && 64BIT - depends on MEMORY_HOTPLUG - depends on MEMORY_HOTREMOVE - depends on SPARSEMEM_VMEMMAP - default y - config MIGRATE_VMA_HELPER bool config DEV_PAGEMAP_OPS bool -config HMM - bool - select MMU_NOTIFIER - select MIGRATE_VMA_HELPER - config HMM_MIRROR bool "HMM mirror CPU page table into a device page table" - depends on ARCH_HAS_HMM - select HMM + depends on (X86...

...nfig ARCH_HAS_HMM_MIRROR - bool - default y - depends on (X86_64 || PPC64) - depends on MMU && 64BIT - -config ARCH_HAS_HMM - bool - depends on (X86_64 || PPC64) - depends on ZONE_DEVICE - depends on MMU && 64BIT - depends on MEMORY_HOTPLUG - depends on MEMORY_HOTREMOVE - depends on SPARSEMEM_VMEMMAP - default y - config MIGRATE_VMA_HELPER bool config DEV_PAGEMAP_OPS bool -config HMM - bool - select MMU_NOTIFIER - select MIGRATE_VMA_HELPER - config HMM_MIRROR bool "HMM mirror CPU page table into a device page table" - depends on ARCH_HAS_HMM - select HMM + depends on MMU...

...I end up with CONFIG_DEVICE_PRIVATE=y in the .config file. make menuconfig tells me: Symbol: ZONE_DEVICE [=n] Type : bool Defined at mm/Kconfig:779 Prompt: Device memory (pmem, HMM, etc...) hotplug support Depends on: MEMORY_HOTPLUG [=n] && MEMORY_HOTREMOVE [=n] && SPARSEMEM_VMEMMAP [=n] && ARCH_HAS_PTE_DEVMAP [=n] Location: (1) -> Memory Management options Selects: XARRAY_MULTI [=n] Pretty obviously a Kconfig whoops, but I have no idea what the proper Kconfig fix is for this.. May be related to: commit 0092908d16c604b8207c2141ec64b0fa4473bb03 Author:...

Hi Dan, Jérôme and Jason, below is a series that cleans up the dev_pagemap interface so that it is more easily usable, which removes the need to wrap it in hmm and thus allowing to kill a lot of code Note: this series is on top of Linux 5.2-rc5 and has some minor conflicts with the hmm tree that are easy to resolve. Diffstat summary: 32 files changed, 361 insertions(+), 1012 deletions(-) Git

Hi Dan, Jérôme and Jason, below is a series that cleans up the dev_pagemap interface so that it is more easily usable, which removes the need to wrap it in hmm and thus allowing to kill a lot of code Diffstat: 22 files changed, 245 insertions(+), 802 deletions(-) Git tree: git://git.infradead.org/users/hch/misc.git hmm-devmem-cleanup Gitweb: