From patchwork Sat May 26 07:16:48 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tao Wang X-Patchwork-Id: 10428865 X-Patchwork-Delegate: rjw@sisk.pl Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 183B2601C7 for ; Sat, 26 May 2018 07:31:24 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id EC4042901D for ; Sat, 26 May 2018 07:31:23 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id DE06129065; Sat, 26 May 2018 07:31:23 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00, MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 0980E2901D for ; Sat, 26 May 2018 07:31:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031171AbeEZHbT (ORCPT ); Sat, 26 May 2018 03:31:19 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:7750 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1031156AbeEZHbT (ORCPT ); Sat, 26 May 2018 03:31:19 -0400 Received: from DGGEMS412-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id A5E5AC5FC2C8F; Sat, 26 May 2018 15:31:01 +0800 (CST) Received: from HSH1000038028.huawei.com (10.177.161.152) by DGGEMS412-HUB.china.huawei.com (10.3.19.212) with Microsoft SMTP Server id 14.3.382.0; Sat, 26 May 2018 15:30:54 +0800 From: Kevin Wangtao To: , CC: , , , , Kevin Wangtao Subject: [PATCH V2] cpufreq: reinitialize new policy min/max when writing scaling_(max|min)_freq Date: Sat, 26 May 2018 15:16:48 +0800 Message-ID: <1527319008-66663-1-git-send-email-kevin.wangtao@hisilicon.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1527144234-96396-1-git-send-email-kevin.wangtao@hisilicon.com> References: <1527144234-96396-1-git-send-email-kevin.wangtao@hisilicon.com> MIME-Version: 1.0 X-Originating-IP: [10.177.161.152] X-CFilter-Loop: Reflected Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP consider such situation, current user_policy.min is 1000000, current user_policy.max is 1200000, in cpufreq_set_policy, other driver may update policy.min to 1200000, policy.max to 1300000. After that, If we input "echo 1300000 > scaling_min_freq", then user_policy.min will be 1300000, and user_policy.max is still 1200000, because the input value is checked with policy.max not user_policy.max. if we get all related cpus offline and online again, it will cause cpufreq_init_policy fail because user_policy.min is higher than user_policy.max. The solution is when user space tries to write scaling_(max|min)_freq, the min/max of new_policy should be reinitialized with min/max of user_policy, like what cpufreq_update_policy does. Signed-off-by: Kevin Wangtao Acked-by: Viresh Kumar --- drivers/cpufreq/cpufreq.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c index b79c532..82123a1 100644 --- a/drivers/cpufreq/cpufreq.c +++ b/drivers/cpufreq/cpufreq.c @@ -697,6 +697,8 @@ static ssize_t store_##file_name \ struct cpufreq_policy new_policy; \ \ memcpy(&new_policy, policy, sizeof(*policy)); \ + new_policy.min = policy->user_policy.min; \ + new_policy.max = policy->user_policy.max; \ \ ret = sscanf(buf, "%u", &new_policy.object); \ if (ret != 1) \