linux-kernel - Re: [PATCH V3] sched/cpufreq: calculate util / cap in advance in map_util

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 29 Jan 2019 11:40:53 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Chunyan Zhang <chunyan.zhang@...soc.com>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Vincent Wang <vincent.wang@...soc.com>,
        Quentin Perret <quentin.perret@....com>,
        linux-kernel@...r.kernel.org, Chunyan Zhang <zhang.lyra@...il.com>
Subject: Re: [PATCH V3] sched/cpufreq: calculate util / cap in advance in
 map_util_freq()

On Mon, Jan 28, 2019 at 02:27:21PM +0800, Chunyan Zhang wrote:
> From: "vincent.wang" <vincent.wang@...soc.com>
> 
> When a task that is in_iowait state is enqueued, cpufreq_update_util()
> will be invoked with SCHED_CPUFREQ_IOWAIT flag. In this case,the value
> of util and cap, which are parameters used in map_util_freq(), will be
> cpu frequency, instead of cpu util and capactiy.

Didn't I tell you to fix the IOWAIT case to not pass in such large
numbers?