Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752794Ab2JDEmK (ORCPT ); Thu, 4 Oct 2012 00:42:10 -0400 Received: from e23smtp07.au.ibm.com ([202.81.31.140]:47394 "EHLO e23smtp07.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752704Ab2JDEmH (ORCPT ); Thu, 4 Oct 2012 00:42:07 -0400 From: Deepthi Dharwar Subject: [PATCH v1 0/3] cpuidle: (pSeries) pseries idle driver fixes. To: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org Cc: benh@kernel.crashing.org Date: Thu, 04 Oct 2012 10:12:01 +0530 Message-ID: <20121004044154.15921.51256.stgit@deepthi.in.ibm.com> User-Agent: StGIT/0.14.3 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit x-cbid: 12100404-0260-0000-0000-000001EF11CE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1218 Lines: 30 The following series consists of a bunch of fixes for cpuidle back-end driver for ppc64 (pSeries) platform. The series applies on 3.6-rc7 and has been tested on ppc64 pSeries POWER7 system with snooze and nap states. With these fixes, avg idle residency for nap on 50 percent idle system increased from 96 to 99.4 percent and idle residency for snooze for the same decreased from 4 to 0.6 percent, determined running spec power benchmark runs. Deepthi Dharwar (3): cpuidle: (POWER) Fix snooze state problem persistant in the current cpuidle design on pseries. cpuidle: (POWER) Fix smt_snooze_delay functionality. cpuidle: (POWER) Fix target residency initialisation in pseries cpuidle arch/powerpc/include/asm/processor.h | 4 + arch/powerpc/kernel/sysfs.c | 2 - arch/powerpc/platforms/pseries/processor_idle.c | 62 +++++++++++------------ 3 files changed, 32 insertions(+), 36 deletions(-) -- Deepthi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/