From patchwork Fri Aug 19 08:25:14 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alex Shi X-Patchwork-Id: 74216 Delivered-To: patch@linaro.org Received: by 10.140.29.52 with SMTP id a49csp195826qga; Fri, 19 Aug 2016 01:25:46 -0700 (PDT) X-Received: by 10.98.31.219 with SMTP id l88mr11924480pfj.155.1471595146204; Fri, 19 Aug 2016 01:25:46 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h3si4011676pfg.65.2016.08.19.01.25.45; Fri, 19 Aug 2016 01:25:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754698AbcHSIZd (ORCPT + 27 others); Fri, 19 Aug 2016 04:25:33 -0400 Received: from mail-pa0-f49.google.com ([209.85.220.49]:35868 "EHLO mail-pa0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754427AbcHSIZa (ORCPT ); Fri, 19 Aug 2016 04:25:30 -0400 Received: by mail-pa0-f49.google.com with SMTP id pp5so14156246pac.3 for ; Fri, 19 Aug 2016 01:25:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=iG6PDn8gjJ1VI/S17xnWNRwZkcgAfceXVe/ZK4oStl8=; b=a1rWDHp2jRQ+go9U4F7rpkaRP/eaGFAXj5U1vEaUjMUXR3Xux/I6nfC3eg38Q2sXeG aQ5SMy4aj60QKxlVpcJEPgJqFUIImQ+BSmiQhPUuxIy6utsNwlmEWUuqRoHWzD50Kgk2 KrNrns4uGJGM6oCEEadYPloPDW5Ws6B6nXe3A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=iG6PDn8gjJ1VI/S17xnWNRwZkcgAfceXVe/ZK4oStl8=; b=X1pJ8w0J/MRaD6cNQOTjhp8UL6h8yO48356v0LsOKHJ0jabTKaWGmzYhSY0Asp3rBl YUYMCTGov1VAozM+KDFDH6NLjyQ3QjM/2SdpTbnGR1YqP2jEjrvT11wwe8+2KspSdCHK qbhMsHsjMUYUbIlP3XJ3LheG0Iv47FbozSLHuEgcjNL2Y2H6XIaOjmaWQPRQiEgXT2Cz TSkrf7TSMwuV1ST5gQwbVjRvSyEITyUARCvwe3MXQMOEpsqgVryOuZ13Vn4WiPVVPr1A 3XwKeR/iIGl/MrBWNkjYtnCO5pglQt8yxc7Q7mQkthS0nL4//Ou/O4PzVDXIzyXH7ujY O9KA== X-Gm-Message-State: AEkoousCBJOiLK2vnGPclMIblyuiM0BEVO6XRO85epzeR5RsXhSyM/fwpC5Dw8EQaimhBsRd X-Received: by 10.66.5.72 with SMTP id q8mr11508856paq.38.1471595129599; Fri, 19 Aug 2016 01:25:29 -0700 (PDT) Received: from localhost.localdomain ([139.59.249.186]) by smtp.gmail.com with ESMTPSA id p4sm4290183pfp.60.2016.08.19.01.25.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 19 Aug 2016 01:25:29 -0700 (PDT) From: Alex Shi Cc: Daniel Lezcano , Rasmus Villemoes , Arjan van de Ven , Rik van Riel , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org (open list) Subject: [PATCH 4/4] cpuidle/menu: add per cpu pm_qos_resume_latency consideration Date: Fri, 19 Aug 2016 16:25:14 +0800 Message-Id: <1471595114-1688-4-git-send-email-alex.shi@linaro.org> X-Mailer: git-send-email 2.8.1.101.g72d917a In-Reply-To: <1471595114-1688-1-git-send-email-alex.shi@linaro.org> References: <1471595114-1688-1-git-send-email-alex.shi@linaro.org> To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kernel or user may have special requirement on cpu response time, like if a interrupt is pinned to a cpu, we don't want the cpu goes too deep sleep. This patch can prevent this thing happen by consider per cpu resume_latency setting in cpu sleep state selection in menu governor. The pm_qos_resume_latency ask device to give reponse in this time. That's similar with cpu cstates' entry_latency + exit_latency. But since most of cpu cstate either has no entry_latency or add it into exit_latency So, we just can restrict this time requirement as states exit_latency. The 0 value of pm_qos_resume_latency is for no limitation according ABI definition. So set the value 1 could get the 0 latency if it's needed. Signed-off-by: Alex Shi To: linux-kernel@vger.kernel.org Cc: Daniel Lezcano Cc: Rasmus Villemoes Cc: Alex Shi Cc: Arjan van de Ven Cc: Rik van Riel Cc: "Rafael J. Wysocki" --- drivers/cpuidle/governors/menu.c | 7 +++++++ 1 file changed, 7 insertions(+) -- 2.8.1.101.g72d917a diff --git a/drivers/cpuidle/governors/menu.c b/drivers/cpuidle/governors/menu.c index bb58e2a..e354880 100644 --- a/drivers/cpuidle/governors/menu.c +++ b/drivers/cpuidle/governors/menu.c @@ -12,6 +12,7 @@ #include #include +#include #include #include #include @@ -281,17 +282,23 @@ again: static int menu_select(struct cpuidle_driver *drv, struct cpuidle_device *dev) { struct menu_device *data = this_cpu_ptr(&menu_devices); + struct device *device = get_cpu_device(dev->cpu); int latency_req = pm_qos_request(PM_QOS_CPU_DMA_LATENCY); int i; unsigned int interactivity_req; unsigned int expected_interval; unsigned long nr_iowaiters, cpu_load; + int resume_latency = dev_pm_qos_read_value(device); if (data->needs_update) { menu_update(drv, dev); data->needs_update = 0; } + /* resume_latency is 0 means no restriction */ + if (resume_latency && resume_latency < latency_req) + latency_req = resume_latency; + /* Special case when user has set very strict latency requirement */ if (unlikely(latency_req == 0)) return 0;