dax_kmem_do_hotplug(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so welcome to the dax_kmem_do_hotplug(9) page from the Kernel API Manual, bestie 💖. This function is dax_kmem_do_hotplug — hotplug memory for dax kmem device. That’s the whole name vibe: one job, hotplug memory for a dax kmem device, periodt.

✨ SYNOPSIS ✨

int dax_kmem_do_hotplug (struct dev_dax *dev_dax , struct dax_kmem_data
       *data , int online_type );

🎀 ARGUMENTS 🎀

  • dev_dax — the dev_dax instance, like the main character of this call 🫶.
  • data — the dax_kmem_data structure with resource tracking. It’s literally tracking the resources.
  • online_type — the online policy to use for the memory blocks, no cap.

💅 DESCRIPTION 💅

Hotplugs all ranges in the dev_dax region as system memory, using the provided online policy: offline, online, online_movable, or online_kernel. That’s the lineup, bestie ✨.

Return vibe check: it returns the number of successfully mapped ranges, or negative error. So it’s either a count that slays or a negative error situation 😭.

🦋 SEE ALSO 🦋

Kernel file: ./drivers/dax/kmem.c — yes, that’s the spot 👑

cute sign-off time 🎀: this page is from ./drivers/dax, dated October 2026, and it’s the dax_kmem_do_hotplug(9) manual entry. mwah 💋

📦 where this page comes from