Messages in this thread | | | Date | Sun, 17 Nov 2019 10:45:49 +0100 | From | Ingo Molnar <> | Subject | Re: [GIT PULL] scheduler fixes |
| |
* Valentin Schneider <valentin.schneider@arm.com> wrote:
> Hi, > > On 16/11/2019 21:37, Ingo Molnar wrote: > > Peter Zijlstra (1): > > sched/core: Avoid spurious lock dependencies > > > > Qais Yousef (1): > > sched/uclamp: Fix incorrect condition > > > > Valentin Schneider (2): > > sched/uclamp: Fix overzealous type replacement > > This one got a v2 (was missing one location), acked by Vincent: > > 20191115103908.27610-1-valentin.schneider@arm.com
I've picked v2 up instead. I suspect it's not really consequential as enums don't really get truncated by compilers, right? Is there any other negative runtime side effect possible from the imprecise enum/uint typing?
> > sched/topology, cpuset: Account for housekeeping CPUs to avoid empty cpumasks > > And this one is no longer needed, as Michal & I understood (IOW the fix in > rc6 is sufficient), see: > > c425c5cb-ba8a-e5f6-d91c-5479779cfb7a@arm.com
Ok.
I'm inclined to just reduce sched/urgent back to these three fixes:
6e1ff0773f49: sched/uclamp: Fix incorrect condition b90f7c9d2198: sched/pelt: Fix update of blocked PELT ordering ff51ff84d82a: sched/core: Avoid spurious lock dependencies
and apply v2 of the uclamp_id type fix to sched/core. This would reduce the risks of a Sunday pull request ...
Thanks,
Ingo
| |