From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-pm@lists.linux-foundation.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Re: Possible problem with device_move()
Date: Thu, 2 Aug 2007 16:58:12 +0200 [thread overview]
Message-ID: <200708021658.12991.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0708021020370.3611-100000@iolanthe.rowland.org>
On Thursday, 2 August 2007 16:24, Alan Stern wrote:
> On Thu, 2 Aug 2007, Rafael J. Wysocki wrote:
>
> > > > Perhaps we should create dpm_active right before the suspend, by really
> > > > traversing the device tree, when we own all device semaphores and no device
> > > > objects can be added/removed?
> > >
> > > We're doing okay the way things are. Changing the order is more likely
> > > to cause new problems than to solve existing ones.
> >
> > Well, my idea is not to change the order, but to create the list from scratch
> > when we need it and not in advance, because creating the list in advance
> > causes problems to appear.
>
> Doing it that way will almost certainly result in a different order
> from the one we have now.
Yes, but wouldn't that order be more accurate?
> And it won't help the EHCI issue, because there the question is which of
> several siblings should come last.
Why not? If the device can indicate something like "place me after that one"
to the code creating the list, we can handle that too.
> > In fact, if the system is never suspended, the list that we create is not even
> > useful for anything.
>
> True. But it doesn't take up much space, especially if PM isn't
> configured. And creating the list doesn't take much time.
Sure.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
next prev parent reply other threads:[~2007-08-02 14:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 15:36 Possible problem with device_move() Alan Stern
2007-07-30 6:42 ` Cornelia Huck
2007-07-30 17:34 ` Alan Stern
2007-07-31 8:33 ` Cornelia Huck
2007-07-31 15:11 ` Alan Stern
2007-07-31 15:27 ` Rafael J. Wysocki
2007-07-31 15:30 ` Cornelia Huck
2007-07-31 18:17 ` Alan Stern
2007-07-31 19:12 ` Rafael J. Wysocki
2007-07-31 20:37 ` Alan Stern
2007-08-01 13:03 ` Cornelia Huck
2007-08-01 15:22 ` Alan Stern
2007-08-01 17:04 ` Cornelia Huck
2007-08-01 17:35 ` Alan Stern
2007-08-01 19:25 ` Rafael J. Wysocki
2007-08-01 20:27 ` Alan Stern
2007-08-02 8:06 ` Cornelia Huck
2007-08-02 14:19 ` Alan Stern
2007-08-02 14:50 ` Cornelia Huck
2007-08-02 11:21 ` Rafael J. Wysocki
2007-08-02 14:24 ` Alan Stern
2007-08-02 14:58 ` Rafael J. Wysocki [this message]
2007-08-02 15:23 ` Alan Stern
2007-08-02 22:39 ` Rafael J. Wysocki
2007-08-03 14:56 ` Alan Stern
2007-08-03 21:39 ` Rafael J. Wysocki
2007-08-06 9:31 ` Cornelia Huck
2007-08-06 13:53 ` Alan Stern
2007-07-30 6:53 ` Marcel Holtmann
2007-07-30 17:37 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200708021658.12991.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cornelia.huck@de.ibm.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=marcel@holtmann.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox