From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] PM / Wakeup: Introduce wakeup source objects and event statistics (was: Re: Wakeup-events implementation)
Date: Thu, 9 Sep 2010 01:58:21 +0200 [thread overview]
Message-ID: <201009090158.21861.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1009081607170.1535-100000@iolanthe.rowland.org>
On Wednesday, September 08, 2010, Alan Stern wrote:
> On Wed, 8 Sep 2010, Rafael J. Wysocki wrote:
>
> > Hi,
> >
> > Below is a patch that adds some statistics to the previously merged
> > pm_wakeup_event()/pm_stay_awake()/pm_relax() code. It also makes it possible
> > to use wakeup sources that are not directly associated with devices.
>
> I noted only a few things during a quick read-through.
Great. :-)
> See below.
>
> > It adds functions for manipulating wakeup source objects and reworks the
> > device wakeup enabling/disabling to use the new functions. The list of wakeup
> > sources is only used for updating the "hit count" statistics for now (this is
> > the number of times the wakeup source was active when the PM core checked), but
> > I'm planning to add a /proc file listing all wakeup sources, including the ones
> > that are not attached to device objects.
>
> It must be obvious that this is starting to look more and more like the
> suspend_blockers patch. What that means or will lead to, I don't
> know...
This actually is intentional, because I want to make it easier for the Android
people to move their stuff towards the mainline, if they want to.
> > It appears to work with the PCI wakeup code added previously, but that's only
> > one case. I'm also not sure if it builds withoug CONFIG_PM_SLEEP. [BTW, I'm
> > not sure it atomic_inc() and atomic_dec() imply a memory barrier in general.
> > That seems to be the case on x86, but I don't know about other architectures.]
>
> They do not imply memory barriers. See the section on atomic
> operations in Documentation/memory-barriers.txt.
Ah. Thanks for the pointer.
> > +/**
> > + * wakeup_source_create - Create a struct wakeup_source object.
> > + * @name: Name of the new wakeup source.
> > + */
> > +struct wakeup_source *wakeup_source_create(const char *name)
> > +{
> > + struct wakeup_source *ws;
> > +
> > + ws = kzalloc(sizeof(*ws), GFP_KERNEL);
> > + if (!ws)
> > + return NULL;
> > +
> > + if (name) {
> > + int len = strlen(name);
> > + char *s = kzalloc(len + 1, GFP_KERNEL);
> > + if (s) {
> > + strncpy(s, name, len);
>
> Would it be better to use kmalloc instead of kzalloc, call memcpy
> instead of strncpy, and write the terminating NUL character manually?
Yeah, thanks.
> > + ws->name = s;
> > + }
> > + }
> > +
> > + return ws;
> > +}
> > +EXPORT_SYMBOL_GPL(wakeup_source_create);
> > +
> > +/**
> > + * wakeup_source_destroy - Destroy a struct wakeup_source object.
> > + * @ws: Wakeup source to destroy.
> > + */
> > +void wakeup_source_destroy(struct wakeup_source *ws)
> > +{
> > + if (!ws)
> > + return;
> > +
> > + spin_lock_irq(&ws->lock);
>
> Since you use the spinlock here, it needs to be initialized in
> wakeup_source_create rather than wakeup_source_register.
Yes, thanks.
> > + while (ws->active) {
> > + spin_unlock_irq(&ws->lock);
> > +
> > + schedule_timeout_interruptible(msecs_to_jiffies(TIMEOUT));
> > +
> > + spin_lock_irq(&ws->lock);
> > + }
> > + spin_unlock_irq(&ws->lock);
> > +
> > + if (ws->name)
> > + kfree(ws->name);
>
> No need for the "if".
OK
> > + kfree(ws);
> > +}
> > +EXPORT_SYMBOL_GPL(wakeup_source_destroy);
> > +
> > +/**
> > + * wakeup_source_register - Add given object to the list of wakeup sources.
> > + * @ws: Wakeup source object to register.
> > + */
> > +void wakeup_source_register(struct wakeup_source *ws)
> > +{
> > + if (WARN_ON(!ws))
> > + return;
> > +
> > + spin_lock_init(&ws->lock);
> > + setup_timer(&ws->timer, pm_wakeup_timer_fn, (unsigned long)ws);
> > + ws->active = false;
> > +
> > + spin_lock_irq(&events_lock);
> > + list_add_rcu(&ws->entry, &wakeup_sources);
> > + spin_unlock_irq(&events_lock);
> > + synchronize_rcu();
> > +}
> > +EXPORT_SYMBOL_GPL(wakeup_source_register);
>
> ...
>
> > +/**
> > + * wakeup_source_add - Create and register a wakeup source object.
> > + * @name: Name of the wakeup source to create.
> > + */
> > +struct wakeup_source *wakeup_source_add(const char *name)
> > +{
> > + struct wakeup_source *ws;
> > +
> > + ws = wakeup_source_create(name);
> > + if (ws)
> > + wakeup_source_register(ws);
> > +
> > + return ws;
> > +}
> > +EXPORT_SYMBOL_GPL(wakeup_source_add);
>
> Your use of names is backward. Normally the *_register routine does
> *_init followed by *_add.
Hmm, I haven't noticed that. Thanks for the heads up. :-)
> I haven't looked through the rest in enough detail yet to make any
> meaningful comments.
Sure. Thanks a lot for your comments so far!
Rafael
next parent reply other threads:[~2010-09-08 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.1009081607170.1535-100000@iolanthe.rowland.org>
2010-09-08 23:58 ` Rafael J. Wysocki [this message]
[not found] <Pine.LNX.4.44L0.1009101119060.1651-100000@iolanthe.rowland.org>
2010-09-10 22:29 ` [RFC][PATCH] PM / Wakeup: Introduce wakeup source objects and event statistics (was: Re: Wakeup-events implementation) Rafael J. Wysocki
[not found] <201009080151.43047.rjw@sisk.pl>
2010-09-08 20:17 ` Alan Stern
2010-09-10 15:21 ` Alan Stern
2010-08-20 15:04 Wakeup-events implementation Alan Stern
2010-09-07 23:51 ` [RFC][PATCH] PM / Wakeup: Introduce wakeup source objects and event statistics (was: Re: Wakeup-events implementation) Rafael J. Wysocki
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=201009090158.21861.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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