On Mon, Jun 09, 2014 at 11:20:27AM +0100, Morten Rasmussen wrote: > On Sun, Jun 08, 2014 at 07:03:16AM +0100, Henrik Austad wrote: > > On Fri, May 23, 2014 at 07:16:29PM +0100, Morten Rasmussen wrote: > > > The Energy-aware scheduler implementation is guarded by > > > CONFIG_SCHED_ENERGY. > > > > > > Signed-off-by: Dietmar Eggemann <[email protected]> > > > Signed-off-by: Morten Rasmussen <[email protected]> > > > --- > > > arch/arm/Kconfig | 5 +++++ > > > 1 file changed, 5 insertions(+) > > > > > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > > > index ab438cb..bfc3a85 100644 > > > --- a/arch/arm/Kconfig > > > +++ b/arch/arm/Kconfig > > > > Is this going to be duplicate for each architecture enabling this? Why > > not make a kernel/Kconfig.energy and link to that from those > > architectures using it? > > kernel/Kconfig.energy is better I think.
Well, strictly speaking I'd prefer to not have more sched CONFIG knobs. Do we really need to have this CONFIG guarded?
pgpu_RPKdW_Uk.pgp
Description: PGP signature
