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]
Date:	Mon, 18 Jan 2010 11:10:16 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	pm list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [RFC][PATCH] PM / Runtime: Add sysfs switch for disabling device
 run-time PM

On Mon, 18 Jan 2010, Rafael J. Wysocki wrote:

> From: Rafael J. Wysocki <rjw@...k.pl>
> Subject: PM / Runtime: Add sysfs switch for disabling device run-time PM
> 
> Add new device sysfs attribute, power/runtime, allowing the user
> space to block the run-time power management of the device.  If this
> attribute is set to "disabled", the driver of the device won't be
> able to enable run-time power management for it (without breaking the
> rules).

Ouch.  This does nearly the same thing as the power/level attribute in
the USB subsystem, but in an incompatible and more complicated way.

The power/level attribute can contain either "on" or "auto", meaning
that the device is always on or that it is subject to automatic runtime
power management (autosuspend).  Changing the setting from "auto" to
"on" merely does sets a flag and does pm_runtime_get_sync(); changing
it from "on" to "auto" clears the flag and does pm_runtime_put_sync().

Is there any reason this same mechanism shouldn't be used for all
devices?

Alan Stern

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ