[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWfSIX5lRqb35yUf@gourry-fedora-PF4VCD3F>
Date: Wed, 14 Jan 2026 12:28:01 -0500
From: Gregory Price <gourry@...rry.net>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>
Cc: linux-mm@...ck.org, linux-cxl@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
kernel-team@...a.com, dan.j.williams@...el.com,
vishal.l.verma@...el.com, dave.jiang@...el.com, mst@...hat.com,
jasowang@...hat.com, xuanzhuo@...ux.alibaba.com,
eperezma@...hat.com, osalvador@...e.de, akpm@...ux-foundation.org
Subject: Re: [PATCH 4/8] mm/memory_hotplug: return online type from
add_memory_driver_managed()
On Wed, Jan 14, 2026 at 11:49:19AM +0100, David Hildenbrand (Red Hat) wrote:
> On 1/14/26 09:51, Gregory Price wrote:
> > Change add_memory_driver_managed() to return the online type (MMOP_*)
> > on success instead of 0. This allows callers to determine the actual
> > online state of the memory after addition, which is important when
> > MMOP_SYSTEM_DEFAULT is used and the actual online type depends on the
> > system default policy.
>
> Another reason to just let the caller handle MMOP_SYSTEM_DEFAULT itself by
> calling mhp_get_default_online_type() :)
>
Yeah i don't even end up using it, this is just cruft from early
iterations. I'll clean it up.
~Gregory
Powered by blists - more mailing lists