From: James Hogan <james@albanarts.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-pm@lists.linux-foundation.org
Cc: Randy Dunlap <rdunlap@xenotime.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Alan Stern <stern@rowland.harvard.edu>,
markgross <markgross@thegnar.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>
Subject: [PATCH v2 0/2] pm_trace: Add locking and add sysfs attr for rechecking dev hash.
Date: Sun, 10 Oct 2010 02:02:00 +0100 [thread overview]
Message-ID: <201010100202.01605.james@albanarts.com> (raw)
A fix and an improvement to the pm_trace code.
The improvement allows finding out via sysfs which device was last traced when
the device is part of a kernel module (which means it doesn't get printed on
next boot since it isn't loaded yet).
Changes in v2:
- renamed sysfs attr pm_trace_dev_hash to pm_trace_dev_match
- renamed snprint_trace_dev_hash to show_trace_dev_match
- added comment in show_trace_dev_match referring to the fact that multiple
devices could match the hash and they all need printing out
- added documentation to Documentation/ABI/testing/sysfs-power
- minor rewording in Documentation/power/s2ram.txt
James Hogan (2):
pm_trace: Lock pm device list mutex.
pm_trace: Add sysfs attr for rechecking dev hash.
Documentation/ABI/testing/sysfs-power | 29 ++++++++++++++++++++++++++
Documentation/power/s2ram.txt | 7 ++++++
drivers/base/power/trace.c | 36 ++++++++++++++++++++++++++++++++-
include/linux/resume-trace.h | 2 +
kernel/power/main.c | 18 ++++++++++++++++
5 files changed, 91 insertions(+), 1 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-10-10 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 1:02 James Hogan [this message]
2010-10-10 1:05 ` [PATCH v2 1/2] pm_trace: Lock pm device list mutex James Hogan
2010-10-10 1:06 ` [PATCH v2 2/2] pm_trace: Add sysfs attr for rechecking dev hash James Hogan
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=201010100202.01605.james@albanarts.com \
--to=james@albanarts.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--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