Re: [PATCH] memremap: move from kernel/ to mm/

2019-07-22 Thread Anshuman Khandual
On 07/22/2019 03:11 PM, Christoph Hellwig wrote: > memremap.c implements MM functionality for ZONE_DEVICE, so it really > should be in the mm/ directory, not the kernel/ one. > > Signed-off-by: Christoph Hellwig This always made sense. FWIW Reviewed-by: Anshu

Re: [PATCH] mm, memory-failure: clarify error message

2019-05-16 Thread Anshuman Khandual
On 05/17/2019 09:38 AM, Jane Chu wrote: > Some user who install SIGBUS handler that does longjmp out What the longjmp about ? Are you referring to the mechanism of catching the signal which was registered ? > therefore keeping the process alive is confused by the error > message >

Re: [RFC PATCH] mm/nvdimm: Fix kernel crash on devm_mremap_pages_release

2019-05-13 Thread Anshuman Khandual
On 05/14/2019 08:23 AM, Aneesh Kumar K.V wrote: > When we initialize the namespace, if we support altmap, we don't initialize > all the > backing struct page where as while releasing the namespace we look at some of > these uninitilized struct page. This results in a kernel crash as below. Yes

Re: [PATCH] arm64: configurable sparsemem section size

2019-04-24 Thread Anshuman Khandual
On 04/25/2019 01:18 AM, Pavel Tatashin wrote: > On Wed, Apr 24, 2019 at 5:07 AM Anshuman Khandual > wrote: >> >> On 04/24/2019 02:08 AM, Pavel Tatashin wrote: >>> sparsemem section size determines the maximum size and alignment that >>> is allowed to off

Re: [PATCH] arm64: configurable sparsemem section size

2019-04-24 Thread Anshuman Khandual
On 04/24/2019 02:08 AM, Pavel Tatashin wrote: > sparsemem section size determines the maximum size and alignment that > is allowed to offline/online memory block. The bigger the size the less > the clutter in /sys/devices/system/memory/*. On the other hand, however, > there is less flexability

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

2017-12-22 Thread Anshuman Khandual
On 12/23/2017 03:43 AM, Ross Zwisler wrote: > On Fri, Dec 22, 2017 at 08:39:41AM +0530, Anshuman Khandual wrote: >> On 12/14/2017 07:40 AM, Ross Zwisler wrote: >>> Quick Summary >>> >>> Platforms exist today which have multiple types of

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

2017-12-22 Thread Anshuman Khandual
On 12/22/2017 10:43 PM, Dave Hansen wrote: > On 12/21/2017 07:09 PM, Anshuman Khandual wrote: >> I had presented a proposal for NUMA redesign in the Plumbers Conference this >> year where various memory devices with different kind of memory attributes >> can be repr

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

2017-12-22 Thread Anshuman Khandual
On 12/22/2017 04:01 PM, Kogut, Jaroslaw wrote: >> ... first thinking about redesigning the NUMA for >> heterogeneous memory may not be a good idea. Will look into this further. > I agree with comment that first a direction should be defined how to handle > heterogeneous memory system. > >>

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

2017-12-21 Thread Anshuman Khandual
On 12/14/2017 07:40 AM, Ross Zwisler wrote: > Quick Summary > > Platforms exist today which have multiple types of memory attached to a > single CPU. These disparate memory ranges have some characteristics in > common, such as CPU cache coherence, but they can have wide ranges of >

Re: [PATCH] mm: add ZONE_DEVICE statistics to smaps

2016-11-10 Thread Anshuman Khandual
On 11/11/2016 03:41 AM, Dan Williams wrote: > ZONE_DEVICE pages are mapped into a process via the filesystem-dax and > device-dax mechanisms. There are also proposals to use ZONE_DEVICE > pages for other usages outside of dax. Add statistics to smaps so > applications can debug that they are