Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756406Ab0FIINw (ORCPT ); Wed, 9 Jun 2010 04:13:52 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:43436 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752986Ab0FIINt (ORCPT ); Wed, 9 Jun 2010 04:13:49 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IKxdPqjYI0qDeLJ98vunIzuaQto5fivEYpcnrKSGYMAFWycGX/izcIH0ommSrGpGxz 92ziVXlUfchEpj5wP0hiQ4TjxjCKcnSPOI6xCfd+jN0Gf69I9phIxKrKOSndE+LqThvf mFB06KWAlh1wZL6rVTp5PpeJBwHTY+9FzomBM= MIME-Version: 1.0 In-Reply-To: <20100605225012.771332db@schatten.dmk.lab> References: <201005312347.24251.rjw@sisk.pl> <1275471561.27810.30865.camel@twins> <1275474088.27810.31000.camel@twins> <20100602221309.6da754e7@schatten.dmk.lab> <1275550802.27810.34863.camel@twins> <20100603161205.73a2b56d@schatten.dmk.lab> <1275578881.27810.35995.camel@twins> <20100605215604.68efc4e5@schatten.dmk.lab> <20100605225012.771332db@schatten.dmk.lab> Date: Wed, 9 Jun 2010 11:13:47 +0300 Message-ID: Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) From: Felipe Contreras To: Florian Mickler Cc: Peter Zijlstra , =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Thomas Gleixner , "Rafael J. Wysocki" , Matthew Garrett , Alan Stern , Paul@smtp1.linux-foundation.org, LKML , felipe.balbi@nokia.com, Linux OMAP Mailing List , Linux PM , Alan Cox Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2170 Lines: 49 On Sat, Jun 5, 2010 at 11:50 PM, Florian Mickler wrote: > On Sat, 5 Jun 2010 23:06:03 +0300 > Felipe Contreras wrote: >> How would such stats be calculated? I presume at regular intervals you >> check which applications are holding suspend blockers and increase a >> counter. >> >> How would you do that with the dynamic PM approach? At regular >> intervals you check for which applications are running (not idle). > > IIRC, the patches discussed have debugging infrastructure in > them. The kernel does the accounting. We are not talking about debugging, we are talking about stats shown in user-space so that users can see the offending apps. It doesn't matter where the accounting is done, it would be at regular intervals and there's nothing that prevents the dynamic PM approach to offer similar stats. >> > The only difference is, that with suspend blockers, he can than >> > dismiss the applications permission to block suspend and will not miss >> > his job interview the next day because his phones battery run >> > out. And also he can use the application to a certain extent. >> >> So the difference is between removing the app, and making it run >> crappy. I don't think that's a strong argument in favor of suspend >> blockers. >> > If you think a little about it, it is. Because if the app wouldn't be > usable at all, the bug wouldn't get fixed because the user wouldn't use > it. Or not? I'm not sure what's your point here. One user not using a certain application doesn't prevent bugs to get fixed. In fact, less people using an app will cause less buzz, and less downloads, and less positive votes... which might wake up the author to think: hey, maybe I'm doing something wrong? Maybe I should really listen to those bug reports. Anyway, my point is that there's nothing special about 3rd party app stats with suspend blockers. -- Felipe Contreras -- 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/