[RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms.

Hi Hanjun,

On Tue, Oct 28, 2014 at 2:18 PM, Hanjun Guo [off-list ref] wrote:

Hi Ganapatrao,

On 2014-10-18 1:19, Ganapatrao Kulkarni wrote:
[...]

quoted

Below is the example for the proposal of numa bindings in DT.
This covers cpu to node mapping, memory ranges to node mapping.
Also defines proximity distance matrix of nodes to each other.
please let me know your comments to go ahead with the implementation.

numa-map{
         /*  Address cells used for memory range base address in mem-map.
             For all others, size-cells is used.
             Node-count tells the number of numa nodes in the system.
         */
         #address-cells = <2>;
         #size-cells = <1>;
         #node-count = <4>;

         /* Memmap for memory ranges on each node>

         mem-map = <0x0   0x00c00000 0>,
           <0x1   0x00000000 1>,
           <0x100 0x00000000 2>,
           <0x200 0x00000000 3>;

         /* CPU to node map for 4 NODE and 16 CPUs system
        < first-cpu last-cpu  node belongs>

What's the property for the cpu? MPIDR of this CPU?

I see in ACPI spec, there is mapping between logical cpu number to
physical id(using MPIDR) using GICC Affinity Structure
Here i am defining mapping between the logical CPUs and the node it belongs.
SMP initialization uses CPU node property of DT to bring them up. We
can get physical id using cpu_logical_map(cpu), which is MPIDR
Do you see any need to expand cpu-map here to have the mapping between
physical cpu id and logical cpu id?

quoted

         */
         cpu-map = <0 3 0>,
                         <4 7 1>,
                        <8 11 2>,
                        <12 16 3>;

Thanks
Hanjun

thanks
ganapat

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel