[PATCH 0/8] Suspend block api (version 8)
in [Kernel]
|
Prev: [ANN] Linux Security Summit 2010 - Announcement and CFP
Next: [PATCH 4/8] PM: suspend_block: Add debugfs file
From: Arve Hjønnevåg on 21 May 2010 18:50 This patch series adds a suspend-block api that provides the same functionality as the android wakelock api. This version adds a delay before suspending again if no suspend blockers were used during the last suspend attempt. -- Arve Hjønnevåg <arve(a)android.com> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Vitaly Wool on 26 May 2010 07:20 On Wed, May 26, 2010 at 12:02 PM, Florian Mickler <florian(a)mickler.org> wrote: >> So why again was this such a great scheme? Go fix your userspace to not >> not run when not needed. > > Hi Peter! > > This was already mentioned in one of these threads. > > The summary is: The device this kernel is running on dosn't want to > (or can) rely on userspace to save power. This is because it is an open > system, without an app-store or the like. Everyone can run what he > wants. I don't see this as a valid point. Everyone can run a different kernel where nothing will just work. Are you aiming protection against that as well? ~Vitaly -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Vitaly Wool on 26 May 2010 07:30 2010/5/26 Arve Hj�nnev�g <arve(a)android.com>: > Fixing the actually issue means fixing all user-space code, and > replacing most x86 hardware. I don't think keeping this feature out of > the kernel will significantly accelerate this. But if this feature gets merged, I bet you'll find another 100 reasons to not fix the actual issue. I wouldn't say so if you haven't provided the irrelevant points already, like "replacing x86 hardware". You're trying to merge the approach which makes the bad way of handing things the easiest way. This shouldn't get in as it is IMO. ~Vitaly -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Florian Mickler on 26 May 2010 07:40 On Wed, 26 May 2010 13:18:51 +0200 Vitaly Wool <vitalywool(a)gmail.com> wrote: > On Wed, May 26, 2010 at 12:02 PM, Florian Mickler <florian(a)mickler.org> wrote: > > >> So why again was this such a great scheme? Go fix your userspace to not > >> not run when not needed. > > > > Hi Peter! > > > > This was already mentioned in one of these threads. > > > > The summary is: The device this kernel is running on dosn't want to > > (or can) rely on userspace to save power. This is because it is an open > > system, without an app-store or the like. Everyone can run what he > > wants. > > I don't see this as a valid point. Everyone can run a different kernel > where nothing will just work. Are you aiming protection against that > as well? > > ~Vitaly This is not "protection". This is functioning properly in a real world scenario. Why would the user change the kernel, if the device would be buggy after that? (Except maybe he is a geek) Cheers, Flo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Felipe Balbi on 26 May 2010 08:40
Hi, On Wed, May 26, 2010 at 02:33:23PM +0200, ext Florian Mickler wrote: >But then someone at the user side has to know what he is doing. > >I fear, if you target mass market without central distribution >channels, you can not assume that much. and that's enough to push hacks into the kernel ? I don't think so. Do it like apple and prevent multi-tasking for any non-apple applications :-p -- balbi DefectiveByDesign.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |