lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20171213090623.GV25177@vireshk-i7> Date: Wed, 13 Dec 2017 14:36:23 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Patrick Bellasi <patrick.bellasi@....com> Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>, "Rafael J . Wysocki" <rafael.j.wysocki@...el.com>, Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, Morten Rasmussen <morten.rasmussen@....com>, Juri Lelli <juri.lelli@...hat.com>, Todd Kjos <tkjos@...roid.com>, Joel Fernandes <joelaf@...gle.com> Subject: Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter On 12-12-17, 15:16, Patrick Bellasi wrote: > Since you are already changing some flags position, maybe we can have > a better organization by using lower flags for "general bits" and > higher ones for class specific, i.e. > > #define SCHED_CPUFREQ_CLEAR (1U << 0) > #define SCHED_CPUFREQ_IOWAIT (1U << 1) > > #define SCHED_CPUFREQ_CFS (1U << 8) > #define SCHED_CPUFREQ_RT (1U << 9) > #define SCHED_CPUFREQ_DL (1U << 10) Since we aren't normally going to add any more of class specific ones, I would like to keep them as 0, 1 and 2. And using the top most bit for CLEAR seems better to me somehow, just like the signed bit for 32 bit integers. -- viresh
Powered by blists - more mailing lists