From: gpkulkarni@gmail.com (Ganapatrao Kulkarni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms.
Date: Wed, 29 Oct 2014 12:50:30 +0530 [thread overview]
Message-ID: <CAFpQJXW1yEeY8+TH74tVsbFW6s1hgUk84XjgH7Cfve_Eewpojw@mail.gmail.com> (raw)
In-Reply-To: <544F586B.6080508@linaro.org>
Hi Hanjun,
On Tue, Oct 28, 2014 at 2:18 PM, Hanjun Guo <hanjun.guo@linaro.org> wrote:
> Hi Ganapatrao,
>
> On 2014-10-18 1:19, Ganapatrao Kulkarni wrote:
> [...]
>> 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?
>
>> */
>> 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
next prev parent reply other threads:[~2014-10-29 7:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 9:03 [RFC PATCH 0/4] arm64:numa: Add numa support for arm64 platforms Ganapatrao Kulkarni
2014-09-25 9:03 ` [RFC PATCH 1/4] arm64: defconfig: increase NR_CPUS range to 2-128 Ganapatrao Kulkarni
2014-10-03 10:58 ` Mark Rutland
2014-10-06 4:29 ` Ganapatrao Kulkarni
2014-09-25 9:03 ` [RFC PATCH 2/4] arm/arm64:dt:numa: adding numa node mapping for memory nodes Ganapatrao Kulkarni
2014-10-03 11:05 ` Mark Rutland
2014-10-06 4:20 ` Ganapatrao Kulkarni
2014-10-06 11:08 ` Mark Rutland
2014-10-06 17:26 ` Ganapatrao Kulkarni
2014-09-25 9:03 ` [RFC PATCH 3/4] arm64:thunder: Add initial dts for Cavium Thunder SoC in 2 Node topology Ganapatrao Kulkarni
2014-10-03 11:19 ` Mark Rutland
2014-09-25 9:03 ` [RFC PATCH 4/4] arm64:numa: adding numa support for arm64 platforms Ganapatrao Kulkarni
2014-10-03 12:13 ` Mark Rutland
2014-10-06 5:14 ` Ganapatrao Kulkarni
2014-10-06 11:26 ` Mark Rutland
2014-10-06 17:52 ` Ganapatrao Kulkarni
2014-10-17 17:19 ` Ganapatrao Kulkarni
2014-10-20 14:25 ` Steve Capper
2014-10-20 14:30 ` Steve Capper
2014-10-22 11:27 ` Ganapatrao Kulkarni
2014-10-28 8:48 ` Hanjun Guo
2014-10-29 7:20 ` Ganapatrao Kulkarni [this message]
2014-09-25 9:04 ` Ganapatrao Kulkarni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFpQJXW1yEeY8+TH74tVsbFW6s1hgUk84XjgH7Cfve_Eewpojw@mail.gmail.com \
--to=gpkulkarni@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).