Hi Michael,
On 04/04/2014 09:18 AM, Michael wang wrote:
Hi, Srivatsa
Thanks for your reply :)
On 04/03/2014 04:50 PM, Srivatsa S. Bhat wrote:
[snip]
Now, the interesting thing to note here is that, if CPU0's node was already
set as node0, *nothing* should go wrong, since its just a
Hi Michael,
On 04/02/2014 08:59 AM, Michael wang wrote:
During the testing, we encounter below WARN followed by Oops:
WARNING: at kernel/sched/core.c:6218
...
NIP [c0101660] .build_sched_domains+0x11d0/0x1200
LR [c0101358]
Hi, Srivatsa
It's nice to have you confirmed the fix, and thanks for the well-writing
comments, will apply them and send out the new patch later :)
Regards,
Michael Wang
On 04/07/2014 06:15 PM, Srivatsa S. Bhat wrote:
Hi Michael,
On 04/02/2014 08:59 AM, Michael wang wrote:
During the
On 04/02/2014 08:59 AM, Michael wang wrote:
During the testing, we encounter below WARN followed by Oops:
WARNING: at kernel/sched/core.c:6218
...
NIP [c0101660] .build_sched_domains+0x11d0/0x1200
LR [c0101358] .build_sched_domains+0xec8/0x1200
Hi, Srivatsa
Thanks for your reply :)
On 04/03/2014 04:50 PM, Srivatsa S. Bhat wrote:
[snip]
Now, the interesting thing to note here is that, if CPU0's node was already
set as node0, *nothing* should go wrong, since its just a redundant update.
However, if CPU0's original node mapping was
During the testing, we encounter below WARN followed by Oops:
WARNING: at kernel/sched/core.c:6218
...
NIP [c0101660] .build_sched_domains+0x11d0/0x1200
LR [c0101358] .build_sched_domains+0xec8/0x1200
PACATMSCRATCH [8000f032]
