On Thu, Jul 17, 2014 at 20:43:16 +0200,
Dietmar Eggemann <dietmar.eggem...@arm.com> wrote:
If you could apply the patch:
https://lkml.org/lkml/2014/7/17/288
and then run it on your machine, that would give us more details, i.e.
the information on which sched_group(s) and in which sched domain
level (SMT and/or DIE) this issue occurs.
Another thing which you could do is to boot with an extra
'earlyprintk=keep sched_debug' in your command line options with a
build containing the cpumask_clear() in build_sched_groups() and
extract the dmesg output of the scheduler-setup code:
I'll see what I can do. I have plans after work today and I don't know
if I'll be awake enough when I get home to followup tonight or early
tomorrow. Worst case will be over the weekend.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/