Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3482549imm; Mon, 4 Jun 2018 04:28:38 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKXV54SbtAQGJq/8ciQImqEEvWj74pvFKIlQ8FyGoGQSmnrdbfFWozut96yvq8BW9Qa6Qev X-Received: by 2002:a62:1013:: with SMTP id y19-v6mr20923274pfi.166.1528111717940; Mon, 04 Jun 2018 04:28:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528111717; cv=none; d=google.com; s=arc-20160816; b=ntYAjyH58ciDE1rMiC9cjcw9JKHsaAnekfgxtIqGXCDPnH46xhvj6kxqGupTNrvSoh e9K058rvj3O/QISuqCZr50j98KnnNNXLYhaDKXlSUc8zKyLTEUjf5Zwao/RhVR+Q5zwZ +CmRZruKkrfmy9TeXC5OLlZN3riPhw8EOVFs3ov5wOMRlsUxf7dk6fQTRUdBi7xulJk4 NfNVwPPR+eB8+VrTUzJpe2usWBWvJveotkqqULwFK6tV3f/3EnII27Dtr0oNShLVNjt3 xyk2UhJyww0xvLk3EGQ7IeqTuOJjeu2ipYxUls0HVyIzmVmbr7KgX6ezlsC3rTWi/Xpm frLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:arc-authentication-results; bh=5BTigS7KDZr38dvkXTdGHunqRDPmJayqI4IypX2Yweo=; b=VgivJah+0LjMTWEvqetGhaDHstnjeMmXP+8igzTt0ctSE0QBX3bcRFiHWanPq9ZlqD dzDxwrY1/tvxniKqeKuDBPeTYQPlApufb6KyRx6j5AV2Dp1mFL6205Atu4l7p3sFh6Ze kaZwe9o/GvPekM4Vks6kCVSZtRRK4WKi3TJGk/jkpwfPM90Ifj0kcjt3CWXpjfK3wnhb 5ExXO18eKDg0anXp3dTsPR+ufjSYBbeII3w6/h7gKaQaGHCRc/qnjSUwYYjUBPWnYNTt LN5CylFFCV3rGoI8ULwtMON4qz+KUZVePuBdKm5wID5/pJ0SBc04qYjyC3PP+LqV/LZB Gl4g== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 2-v6si2186160pfj.6.2018.06.04.04.28.23; Mon, 04 Jun 2018 04:28:37 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752360AbeFDL1r (ORCPT + 99 others); Mon, 4 Jun 2018 07:27:47 -0400 Received: from ozlabs.org ([203.11.71.1]:58065 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751597AbeFDL1p (ORCPT ); Mon, 4 Jun 2018 07:27:45 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 40zt2j6h1Rz9ryk; Mon, 4 Jun 2018 21:27:41 +1000 (AEST) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au From: Michael Ellerman To: "Gautham R. Shenoy" , "Rafael J. Wysocki" , Daniel Lezcano , Stewart Smith , Michael Neuling , Vaidyanathan Srinivasan , Shilpasri G Bhat , Akshay Adiga , Nicholas Piggin Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, "Gautham R. Shenoy" Subject: Re: [PATCH] cpuidle:powernv: Make the snooze timeout dynamic. In-Reply-To: <1527768909-32637-1-git-send-email-ego@linux.vnet.ibm.com> References: <1527768909-32637-1-git-send-email-ego@linux.vnet.ibm.com> Date: Mon, 04 Jun 2018 21:27:40 +1000 Message-ID: <87fu22bxlf.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Gautham R. Shenoy" writes: > From: "Gautham R. Shenoy" > > The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of > snooze to deeper idle state") introduced a timeout for the snooze idle > state so that it could be eventually be promoted to a deeper idle > state. The snooze timeout value is static and set to the target > residency of the next idle state, which would train the cpuidle > governor to pick the next idle state eventually. > > The unfortunate side-effect of this is that if the next idle state(s) > is disabled, the CPU will forever remain in snooze, despite the fact > that the system is completely idle, and other deeper idle states are > available. That sounds like a bug, I'll add? Fixes: 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze to deeper idle state") Cc: stable@vger.kernel.org # v4.2+ cheers