linux-kernel - Re: [RFC PATCH v2 1/3] PM / Core: suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201104262336.56347.rjw@sisk.pl>
Date:	Tue, 26 Apr 2011 23:36:56 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Greg KH <gregkh@...e.de>, MyungJoo Ham <myungjoo.ham@...sung.com>,
	linux-pm@...ts.linux-foundation.org,
	Len Brown <len.brown@...el.com>,
	"Jean Delvare (PC drivers core)" <khali@...ux-fr.org>,
	"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
	kyungmin.park@...sung.com, myungjoo.ham@...il.com,
	LKML <linux-kernel@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM.

On Tuesday, April 26, 2011, Pavel Machek wrote:
> Hi!
> 
> > > > What is the root problem that this is trying to solve?
> > > 
> > > It is trying to fix machines that need to run periodic kernel tasks
> > > even when user asked them to sleep. Zaurus needs to periodicaly wake
> > > up to be able to charge battery in s2ram state, for example.
> > 
> > Well, if you wake up periodically, it's not S2RAM any more, I'd say.
> 
> It certainly looks a lot like s2ram to the user.
> 
> Now, your PC wakes up periodically in s2ram, too; but it is keyboard
> controller that wakes up, not CPU, so you do not know.

I seriously doubt it's a keyboard controller in contemporary machines.

Yes, there are parts of them that don't actually sleep, but that's not
under OS control.

> On Zaurus, you do not know, either; nothing visible happens and
> userspace is shielded from these details.

If you wake up device drivers, it _is_ visible.  Maybe not to user
space, but that's a semantic difference.

> Should user really have to know if battery charger is implemented on
> keyboard controller or on main cpu before he selects which interface
> to use?

Please don't confuse user space with the user.  You can resume all the
way to user space without turning the backlight on and the user will not
notice, right?

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/