linux-kernel - Re: [PATCH update x2] PM: Introduce core framework for run-time PM of I/O devices (rev. 13)

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: <Pine.LNX.4.44L0.0908082219380.27004-100000@netrider.rowland.org>
Date:	Sat, 8 Aug 2009 22:28:37 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
	Magnus Damm <magnus.damm@...il.com>, Greg KH <gregkh@...e.de>,
	Pavel Machek <pavel@....cz>, Len Brown <lenb@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH update x2] PM: Introduce core framework for run-time PM
 of I/O devices (rev. 13)

On Sat, 8 Aug 2009, Rafael J. Wysocki wrote:

> > The problem with this is that it calls pm_runtime_disable() at a time 
> > when the driver is still supposed to be in control of the device.  
> > Interfering with the driver's legitimate activity in this way is a bad 
> > thing to do.
> > 
> > The difficulty here is that our requirements are a little
> > contradictory.  We want to prevent all runtime PM callbacks while the
> > remove method is running, but we also want the remove method to be able
> > to carry out its own runtime PM activities.
> > 
> > So maybe what we really need is more like a barrier.  That is,
> > something that will do a "get", wait for outstanding callbacks to
> > finish, carry out a resume if one is pending, and cancel other pending
> > requests.  This could easily share code with pm_runtime_disable.  We 
> > should be able to use this for both probe and remove.
> 
> Isn't it what's done in rev. 14?
> 
> pm_runtime_disable(dev);
> pm_runtime_get_noresume(dev);
> pm_runtime_enable(dev);
> 
> is exactly a barrier like this.

It's not exactly the same because it disables runtime PM for a short 
time.  A barrier never disables runtime PM.

>  How exactly would you like to implement it
> instead?

As described above.  The barrier would be equivalent to
pm_runtime_get_noresume followed by pm_runtime_disable except that it
wouldn't actually disable anything.

> > Perhaps this means we don't want to disable runtime PM during system
> > sleep callbacks, but instead use the "barrier" scheme.
> 
> I'm not really sure about that.  I'd rather do what's right now in the patch
> (well, that's why it's in there) until drivers and bus types start using the
> runtime PM framework.  If it turns out to be problematic, we'll change it
> later.

All right.  Since it involves a race, the problem may not show up for a
while.

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/