mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 1/2] PM / Wakeup: Introduce wakeup source objects and event statistics (v3)
Date: Mon, 20 Sep 2010 11:59:08 -0700	[thread overview]
Message-ID: <20100920185908.GA29380@suse.de> (raw)
In-Reply-To: <201009201959.10070.rjw@sisk.pl>

On Mon, Sep 20, 2010 at 07:59:09PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
> Subject: PM / Wakeup: Introduce wakeup source objects and event statistics (v3)
> 
> Introduce struct wakeup_source for representing system wakeup sources
> within the kernel and for collecting statistics related to them.
> Make the recently introduced helper functions pm_wakeup_event(),
> pm_stay_awake() and pm_relax() use struct wakeup_source objects
> internally, so that wakeup statistics associated with wakeup devices
> can be collected and reported in a consistent way (the definition of
> pm_relax() is changed, which is harmless, because this function is
> not called directly by anyone yet).  Introduce new wakeup-related
> sysfs device attributes in /sys/devices/.../power for reporting the
> device wakeup statistics.
> 
> Change the global wakeup events counters event_count and
> events_in_progress into atomic variables, so that it is not necessary
> to acquire a global spinlock in pm_wakeup_event(), pm_stay_awake()
> and pm_relax(), which should allow us to avoid lock contention in
> these functions on SMP systems with many wakeup devices.
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>

Acked-by: Greg Kroah-Hartman <gregkh@suse.de>

Nice job!

  reply	other threads:[~2010-09-20 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20 17:57 [PATCH 0/2] PM: Wakeup sources and async suspend error path bug fix Rafael J. Wysocki
2010-09-20 17:59 ` [PATCH 1/2] PM / Wakeup: Introduce wakeup source objects and event statistics (v3) Rafael J. Wysocki
2010-09-20 18:59   ` Greg KH [this message]
2010-09-20 18:00 ` [PATCH 2/2] PM: Fix potential issue with failing asynchronous suspend Rafael J. Wysocki
2010-09-20 18:59   ` Greg KH
2010-09-22 23:00 ` [PATCH 0/2] PM: Wakeup sources and async suspend error path bug fix Rafael J. Wysocki
2010-10-03 22:04 ` [linux-pm] " mark gross
2010-10-03 23:04   ` Rafael J. Wysocki
2010-10-04  3:29     ` mark gross
2010-10-04 20:30       ` 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=20100920185908.GA29380@suse.de \
    --to=gregkh@suse.de \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --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

Powered by JetHome