From patchwork Thu Aug 25 08:42:42 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alex Shi X-Patchwork-Id: 9298965 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 E18CD60757 for ; Thu, 25 Aug 2016 08:45:38 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id D255A291C1 for ; Thu, 25 Aug 2016 08:45:38 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id C74C129204; Thu, 25 Aug 2016 08:45:38 +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=-6.8 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_HI,T_DKIM_INVALID autolearn=unavailable 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 BF4FF291C1 for ; Thu, 25 Aug 2016 08:45:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933722AbcHYIor (ORCPT ); Thu, 25 Aug 2016 04:44:47 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:34874 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933618AbcHYInk (ORCPT ); Thu, 25 Aug 2016 04:43:40 -0400 Received: by mail-pa0-f54.google.com with SMTP id hb8so15112766pac.2 for ; Thu, 25 Aug 2016 01:42:58 -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=xxL1Y6muznBh0MWFLL2Q1RZ1LqDVM/9dgZMGjPgb6Tg=; b=UVzqZcYO+Lo5ygjde79Lc7Im8Y9sEcH7nyAh9yogG4JNKzGlLelu1GawFd26yEBi0E qEmbs4cR4+0ykF/yBLkNuwDz4QLWbzUPvjmNIL3qvB2Uw7MG+7zZKIP+L/2L/QZyqkkM McMm54Js5G4eCS4kk67ht2ooUpCS6ftHBohCQ= 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=xxL1Y6muznBh0MWFLL2Q1RZ1LqDVM/9dgZMGjPgb6Tg=; b=UcM/Wssh1Y9r+rQWCcAjkvMF34pCnZDd/YtDWFxlSgVJlVOxSnzE7bdXELPgQVzLZN 043Wbqv6WgU4twWtcVApJlI2MOQQfug++J/2ra3q4RIGRNcTcMO6nekGBQ8dzxi4pDRe kz1S2ZDFP4uEfSg1omot0IuCGfPqbq/rSFFl5QfMLiC0VCXXmI/ZzZZdb10AxKoQJUoR +t7uVcwIsJ6dcb+UtR5OFQY+k/G9c8KniHxVp2wqmerKgCG0AaMuBx9K4LfLuD4eW0mi 0sSnvV6+geYLKPdYKTtONec5W5VGp4s3qk8aNLp+00JA2Asg2Fevqw6LKCowb4NiWIrA koYg== X-Gm-Message-State: AE9vXwMwWIWgvL+iyOmJMzI01+qhFlxgFPMokSeyReiivWhqUwRPEwlmxxNxzvDkbWnMR/Rm X-Received: by 10.66.148.7 with SMTP id to7mr14120305pab.128.1472114578225; Thu, 25 Aug 2016 01:42:58 -0700 (PDT) Received: from localhost.localdomain ([139.59.249.186]) by smtp.gmail.com with ESMTPSA id h66sm19016433pfe.58.2016.08.25.01.42.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 25 Aug 2016 01:42:57 -0700 (PDT) From: Alex Shi To: linux-kernel@vger.kernel.org (open list) Cc: linux-pm@vger.kernel.org, Ulf Hansson , Daniel Lezcano , Rasmus Villemoes , Arjan van de Ven , Rik van Riel , "Rafael J. Wysocki" Subject: [PATCH 4/4] cpuidle/menu: add per cpu pm_qos_resume_latency consideration Date: Thu, 25 Aug 2016 16:42:42 +0800 Message-Id: <1472114562-2736-4-git-send-email-alex.shi@linaro.org> X-Mailer: git-send-email 2.8.1.101.g72d917a In-Reply-To: <1472114562-2736-1-git-send-email-alex.shi@linaro.org> References: <1472114562-2736-1-git-send-email-alex.shi@linaro.org> 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 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: linux-pm@vger.kernel.org Cc: Ulf Hansson Cc: Daniel Lezcano Cc: Alex Shi Cc: Rasmus Villemoes Cc: Arjan van de Ven Cc: Rik van Riel Cc: "Rafael J. Wysocki" --- drivers/cpuidle/governors/menu.c | 7 +++++++ 1 file changed, 7 insertions(+) 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;