On 1/15/26 18:42, Gregory Price wrote:
On Thu, Jan 15, 2026 at 06:26:21PM +0100, David Hildenbrand (Red Hat) wrote:
On 1/15/26 00:50, Gregory Price wrote:
The dax kmem driver currently onlines memory automatically during
probe using the system's default online policy but provides no way
to control or query the entire region state at runtime.
This series adds a sysfs interface to control DAX kmem memory
hotplug state, and refactors the memory_hotplug paths to make it
possible for drivers to request an online type at hotplug time.
Gregory, slow down a bit please. I haven't even had the chance to go through
your replies on v1.
Sorry, i realized your feedback on v1 showed there was just too much
complexity. I would ignore v1 entirely at this point, this version is
significantly simpler.
Fair enough, I can see that the complexity here is likely reduced (less
patches! ).
I'm currently on PTO and don't have the full day to review stuff :) And boy
oh boy, do I have a lot of stuff in my inbox.
Maybe given this is the second time the patch subject is suboptimal is
another sign to slow down a bit? :P
Apologies, and I will let this one sit.
Yes, at least wait until I had the chance to reply :)
--
Cheers
David