Re: [PATCH v5 00/36] Private Memory NUMA Nodes
Gregory Price <[email protected]>
| Newsgroups | dev.linux.lists.nvdimm,dev.linux.lists.damon,dev.linux.lists.driver-core,org.kernel.vger.cgroups,org.kernel.vger.kvm,org.kernel.vger.linux-cxl,org.kernel.vger.linux-debuggers,org.kernel.vger.linux-doc,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kvack.linux-mm |
|---|---|
| Message-ID | <an8Xrb5Phmvs0xE4@fedora> |
On Thu, Aug 13, 2026 at 10:55:13AM +0200, Pankaj Gupta wrote: > > > > A device driver could very well just call memory-hotplug directly, > > or its memory could be brought up as a private node via a boot > > paremeter (which I have sculpted for v7). The former is preferred, > > but there's a bit of a chicken/egg scenario for bootstrapping. > > I find this interesting as this appears to be evolving towards a vendor > agnostic framework for hotplugging memory directly to private nodes. > Agnostic would depend on a common standard for such devices. Otherwise, there is still a need for per-device drivers - but hopefully the interaction itself can be generalized. > How you see this working? In particular, How would the kernel know which > memory ranges correspond to HBM or other device memory? > Device marks the region reserved at boot, driver hotplugs. or Device marks the region normal, but boot param sets the node private. > Please also CC me when you post v7: [email protected] > Sure ~Gregory