On 2017/9/4 23:51, Jerome Glisse wrote: > On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote: >> On 2017/8/17 8:05, Jérôme Glisse wrote: >>> Unlike unaddressable memory, coherent device memory has a real >>> resource associated with it on the system (as CPU can address >>> it). Add a new helper to hotplug such memory within the HMM >>> framework. >>> >> >> Got an new question, coherent device( e.g CCIX) memory are likely reported to OS >> through ACPI and recognized as NUMA memory node. >> Then how can their memory be captured and managed by HMM framework? >> > > Only platform that has such memory today is powerpc and it is not reported > as regular memory by the firmware hence why they need this helper. > > I don't think anyone has defined anything yet for x86 and acpi. As this is Not yet, but now the ACPI spec has Heterogeneous Memory Attribute Table (HMAT) table defined in ACPI 6.2. The HMAT can cover CPU-addressable memory types(though not non-cache coherent on-device memory). Ross from Intel already done some work on this, see: https://lwn.net/Articles/724562/ arm64 supports APCI also, there is likely more this kind of device when CCIX is out (should be very soon if on schedule). > memory on PCIE like interface then i don't expect it to be reported as NUMA > memory node but as io range like any regular PCIE resources. Device driver > through capabilities flags would then figure out if the link between the > device and CPU is CCIX capable if so it can use this helper to hotplug it > as device memory. > >From my point of view, Cache coherent device memory will popular soon and reported through ACPI/UEFI. Extending NUMA policy still sounds more reasonable to me. -- Thanks, Bob Liu -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
