Re: [PATCH 3/3] dax/kmem: Always enroll hotplugged memory for memmap_on_memory

2023-07-13 Thread David Hildenbrand
On 13.07.23 08:45, Verma, Vishal L wrote: On Tue, 2023-07-11 at 17:21 +0200, David Hildenbrand wrote: On 11.07.23 16:30, Aneesh Kumar K.V wrote: David Hildenbrand writes: Maybe the better alternative is teach add_memory_resource()/try_remove_memory() to do that internally. In the add_memory

Re: [PATCH 3/3] dax/kmem: Always enroll hotplugged memory for memmap_on_memory

2023-07-13 Thread Verma, Vishal L
On Thu, 2023-07-13 at 09:23 +0200, David Hildenbrand wrote: > On 13.07.23 08:45, Verma, Vishal L wrote: > > > > I'm taking a shot at implementing the splitting internally in > > memory_hotplug.c. The caller (kmem) side does become trivial with this > > approach, but there's a slight complication i

Re: [PATCH v7 7/9] acpi/nfit: Move handler installing logic to driver

2023-07-13 Thread Rafael J. Wysocki
On Mon, Jul 3, 2023 at 10:03 AM Michal Wilczynski wrote: > > Currently logic for installing notifications from ACPI devices is > implemented using notify callback in struct acpi_driver. Preparations > are being made to replace acpi_driver with more generic struct > platform_driver, which doesn't c

Re: [PATCH 3/3] dax/kmem: Always enroll hotplugged memory for memmap_on_memory

2023-07-13 Thread David Hildenbrand
On 13.07.23 17:15, Verma, Vishal L wrote: On Thu, 2023-07-13 at 09:23 +0200, David Hildenbrand wrote: On 13.07.23 08:45, Verma, Vishal L wrote: I'm taking a shot at implementing the splitting internally in memory_hotplug.c. The caller (kmem) side does become trivial with this approach, but the

Re: [PATCH v7 8/9] acpi/nfit: Remove unnecessary .remove callback

2023-07-13 Thread Rafael J. Wysocki
On Mon, Jul 3, 2023 at 10:03 AM Michal Wilczynski wrote: > > Nfit driver doesn't use .remove() callback and provide an empty function > as it's .remove() callback. Remove empty acpi_nfit_remove() and > initialization of callback. > > Suggested-by: Dan Williams > Signed-off-by: Michal Wilczynski

Re: [PATCH 3/3] dax/kmem: Always enroll hotplugged memory for memmap_on_memory

2023-07-13 Thread Verma, Vishal L
On Thu, 2023-07-13 at 17:23 +0200, David Hildenbrand wrote: > On 13.07.23 17:15, Verma, Vishal L wrote: > > On Thu, 2023-07-13 at 09:23 +0200, David Hildenbrand wrote: > > > On 13.07.23 08:45, Verma, Vishal L wrote: > > > > > > > > I'm taking a shot at implementing the splitting internally in > >

Re: [PATCH 3/3] dax/kmem: Always enroll hotplugged memory for memmap_on_memory

2023-07-13 Thread David Hildenbrand
On 13.07.23 17:40, Verma, Vishal L wrote: On Thu, 2023-07-13 at 17:23 +0200, David Hildenbrand wrote: On 13.07.23 17:15, Verma, Vishal L wrote: On Thu, 2023-07-13 at 09:23 +0200, David Hildenbrand wrote: On 13.07.23 08:45, Verma, Vishal L wrote: I'm taking a shot at implementing the splittin

Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

2023-07-13 Thread Jeff Moyer
David Hildenbrand writes: > On 16.06.23 00:00, Vishal Verma wrote: >> The dax/kmem driver can potentially hot-add large amounts of memory >> originating from CXL memory expanders, or NVDIMMs, or other 'device >> memories'. There is a chance there isn't enough regular system memory >> available to