Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756057Ab0FFK5m (ORCPT ); Sun, 6 Jun 2010 06:57:42 -0400 Received: from www.tglx.de ([62.245.132.106]:42495 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755039Ab0FFK5k (ORCPT ); Sun, 6 Jun 2010 06:57:40 -0400 Date: Sun, 6 Jun 2010 12:56:59 +0200 (CEST) From: Thomas Gleixner To: =?ISO-8859-15?Q?Arve_Hj=F8nnev=E5g?= cc: "Rafael J. Wysocki" , Peter Zijlstra , Ingo Molnar , tytso@mit.edu, Brian Swetland , Neil Brown , Alan Stern , Felipe Balbi , LKML , Florian Mickler , Linux OMAP Mailing List , Linux PM , Alan Cox , James Bottomley , Linus Torvalds , Kevin Hilman , "H. Peter Anvin" , Arjan van de Ven Subject: Re: suspend blockers & Android integration In-Reply-To: Message-ID: References: <20100603193045.GA7188@elte.hu> <20100603232302.GA16184@elte.hu> <1275644619.27810.39462.camel@twins> <201006050138.30859.rjw@sisk.pl> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-455178742-1275821822=:2933" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1740 Lines: 47 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-455178742-1275821822=:2933 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Sat, 5 Jun 2010, Arve Hj?nnev?g wrote: > 2010/6/5 Thomas Gleixner : > > > > Can you please explain in a consistent way how the application stack > > and the underlying framework (which exists according to android docs) > > is handling events and how the separation of trust level works ? > > > > I don't think I can, since I only know small parts of it. I know some Sigh, thats the whole reason why this discussion goes nowhere. How in heavens sake should we be able to decide whether suspend blockers are the right and only thing which solves a problem, when the folks advocating suspend blockers are not able to explain the problem in the first place ? > events like input event go though a single thread in our system > process, while other events like network packets (which are also > wakeup events) goes directly to the app. Yes, we know that already, but that's a completely useless information as it does not describe the full constraints and dependencies. Lemme summarize: Android needs suspend blockers, because it works, but cannot explain why it works and why it only works that way. A brilliant argument to merge them - NOT. Thanks, tglx --8323328-455178742-1275821822=:2933-- -- 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/