From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Len Brown <len.brown@intel.com>,
linux-pm <linux-pm@lists.linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] pm: make PM_TRACE more architecture independent
Date: Thu, 8 Nov 2007 16:36:25 +0100 [thread overview]
Message-ID: <200711081636.25987.rjw@sisk.pl> (raw)
In-Reply-To: <1194523015.6294.3.camel@johannes.berg>
On Thursday, 8 of November 2007, Johannes Berg wrote:
> When trying to debug a suspend failure I started implementing
> PM_TRACE for powerpc. I then noticed that I'm debugging a suspend
> failure and so PM_TRACE isn't useful at all, but thought that
> nonetheless this could be useful in the future.
>
> Basically, to support PM_TRACE, you add a Kconfig option that
> selects PM_TRACE and provides the infrastructure as per the
> help text of PM_TRACE.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> Cc: linux-pm@lists.linux-foundation.org
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> ---
> I don't really care much. I can let this patch collect dust until I
> actually want to implement PM_TRACE for powerpc or another architecture
> but since I had it I wanted to send it out too.
>
> drivers/base/power/Makefile | 2 +-
> kernel/power/Kconfig | 23 ++++++++++++++++++++++-
> 2 files changed, 23 insertions(+), 2 deletions(-)
>
> --- everything.orig/drivers/base/power/Makefile 2007-11-08 12:07:09.843121635 +0100
> +++ everything/drivers/base/power/Makefile 2007-11-08 12:19:23.593081000 +0100
> @@ -1,6 +1,6 @@
> obj-y := shutdown.o
> obj-$(CONFIG_PM_SLEEP) += main.o sysfs.o
> -obj-$(CONFIG_PM_TRACE) += trace.o
> +obj-$(CONFIG_PM_TRACE_RTC) += trace.o
>
> ifeq ($(CONFIG_DEBUG_DRIVER),y)
> EXTRA_CFLAGS += -DDEBUG
> --- everything.orig/kernel/power/Kconfig 2007-11-08 12:04:51.443081271 +0100
> +++ everything/kernel/power/Kconfig 2007-11-08 12:12:53.863072157 +0100
> @@ -44,9 +44,30 @@ config PM_VERBOSE
> ---help---
> This option enables verbose messages from the Power Management code.
>
> +config CAN_PM_TRACE
> + def_bool y
> + depends on PM_DEBUG && PM_SLEEP && EXPERIMENTAL
> +
> config PM_TRACE
> + bool
> + help
> + This enables code to save the last PM event point across
> + reboot. The architecture needs to support this, x86 for
> + example does by saving things in the RTC, see below.
> +
> + The architecture specific code must provide the extern
> + functions from <linux/resume-trace.h> as well as the
> + <asm/resume-trace.h> header with a TRACE_RESUME() macro.
> +
> + The way the information is presented is architecture-
> + dependent, x86 will print the information during a
> + late_initcall.
> +
> +config PM_TRACE_RTC
> bool "Suspend/resume event tracing"
> - depends on PM_DEBUG && X86 && PM_SLEEP && EXPERIMENTAL
> + depends on CAN_PM_TRACE
> + depends on X86
> + select PM_TRACE
> default n
> ---help---
> This enables some cheesy code to save the last PM event point in the
>
>
>
>
--
"Premature optimization is the root of all evil." - Donald Knuth
prev parent reply other threads:[~2007-11-08 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 11:56 [PATCH] pm: make PM_TRACE more architecture independent Johannes Berg
2007-11-08 15:36 ` Rafael J. Wysocki [this message]
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=200711081636.25987.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=johannes@sipsolutions.net \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=torvalds@linux-foundation.org \
/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