Hi Inami-san, On Tue, Feb 27, 2018 at 3:19 AM, Gaku Inami <gaku.inami.xh@xxxxxxxxxxx> wrote: > Some R-Car SoCs support big LITTLE architecture produced by ARM, that > have different power/performance characteristics between each CPUs. > In order to aware such as difference, this patch changes the sched > domain flags that the tasks can be scheduled with capacity awareness. > If you use big LITTLE without this patch, the scheduler may make > unintended behaviors. > > Signed-off-by: Gaku Inami <gaku.inami.xh@xxxxxxxxxxx> Thanks for your patch! > --- /dev/null > +++ b/drivers/soc/renesas/rcar-topology.c > @@ -0,0 +1,36 @@ > +// SPDX-License-Identifier: GPL-2.0 > +/* > + * R-Car CPU topology for ARM big.LITTLE platforms > + * > + * Copyright (C) 2018 Renesas Electronics Corporation. > + * > + */ > + > +#include <linux/cpuset.h> > +#include <linux/init.h> > +#include <linux/of.h> > +#include <linux/sched/topology.h> > +#include <linux/topology.h> > + > +static int rcar_cpu_cpu_flags(void) > +{ > + return SD_ASYM_CPUCAPACITY; > +} > + > +static struct sched_domain_topology_level rcar_topology[] = { > +#ifdef CONFIG_SCHED_MC > + { cpu_coregroup_mask, cpu_core_flags, SD_INIT_NAME(MC) }, > +#endif > + { cpu_cpu_mask, rcar_cpu_cpu_flags, SD_INIT_NAME(DIE) }, > + { NULL, } > +}; > + > +static int __init rcar_topology_init(void) > +{ > + if (of_machine_is_compatible("renesas,r8a7795") || > + of_machine_is_compatible("renesas,r8a7796")) > + set_sched_topology(rcar_topology); > + > + return 0; > +} > +early_initcall(rcar_topology_init); None of the above seems R-Car specific to me. So please explain why this can't just be added to arch/arm64/kernel/topology.c instead, and enabled unconditionally. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html