From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753541Ab0ETFNG (ORCPT ); Thu, 20 May 2010 01:13:06 -0400 Received: from smtp.nokia.com ([192.100.122.233]:42119 "EHLO mgw-mx06.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752630Ab0ETFNE (ORCPT ); Thu, 20 May 2010 01:13:04 -0400 Date: Thu, 20 May 2010 07:49:26 +0300 From: Felipe Balbi To: "ext Rafael J. Wysocki" Cc: "Balbi Felipe (Nokia-D/Helsinki)" , ext James Bottomley , "me@felipebalbi.com" , Kevin Hilman , Alan Stern , "linux-omap@vger.kernel.org" , "Theodore Ts'o" , Geoff Smith , Brian Swetland , Kernel development list , Oleg Nesterov , Mark Brown , Tejun Heo , Linux-pm mailing list , Arjan van de Ven , Liam Girdwood , Matthew Garrett , Andrew Morton , Linus Torvalds Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) Message-ID: <20100520044926.GB6773@nokia.com> Reply-To: felipe.balbi@nokia.com References: <1274115885.4418.59.camel@mulgrave.site> <1274191188.10304.5.camel@mulgrave.site> <20100519065934.GH12879@nokia.com> <201005192242.55706.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <201005192242.55706.rjw@sisk.pl> User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 20 May 2010 04:51:38.0123 (UTC) FILETIME=[218AEDB0:01CAF7D8] X-Nokia-AV: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, May 19, 2010 at 10:42:55PM +0200, ext Rafael J. Wysocki wrote: >Please note that this approach is not too practical for vendors who ship >systems like cell phones to the general public. yeah, tell me about it :-p during development on MeeGo devices we try to tackle down as much as possible the use_time offenders and start by filing bugs to those apps, instead of fixing their issues in kernel space. if suspend_blockers could at least be transparent to applications, then it wouldn't be the best scenario but at least applications wouldn't have to be specially written to support that. And like I said, if anyone can hold a suspend_blocker forever the idea of "improving use_time" is easy to break, but then someone replied "anyone holding a suspend_blocker will show up in UI", and again I say you don't need suspend_blockers to have a fancy UI showing which processes are waking up the processor. Powertop already gathers that information, you just need to make a fancy UI around it. -- balbi DefectiveByDesign.org