[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100423135853.478af057.randy.dunlap@oracle.com>
Date: Fri, 23 Apr 2010 13:58:53 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Arve Hjønnevåg <arve@...roid.com>
Cc: linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 5/9] PM: suspend_block: Add debugfs file
On Thu, 22 Apr 2010 18:08:54 -0700 Arve Hjønnevåg wrote:
> Report active and inactive suspend blockers in
> /sys/kernel/debug/suspend_blockers.
This looks more like user interface information than it does debug information.
If that's correct, it shouldn't be in debugfs.
> Signed-off-by: Arve Hjønnevåg <arve@...roid.com>
> ---
> kernel/power/suspend_blocker.c | 44 ++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 42 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/power/suspend_blocker.c b/kernel/power/suspend_blocker.c
> index 868e8f1..047e910 100644
> --- a/kernel/power/suspend_blocker.c
> +++ b/kernel/power/suspend_blocker.c
> @@ -17,6 +17,7 @@
> #include <linux/rtc.h>
> #include <linux/suspend.h>
> #include <linux/suspend_blocker.h>
> +#include <linux/debugfs.h>
> #include "power.h"
>
> enum {
> @@ -41,6 +42,7 @@ struct workqueue_struct *suspend_work_queue;
> struct suspend_blocker main_suspend_blocker;
> static suspend_state_t requested_suspend_state = PM_SUSPEND_MEM;
> static bool enable_suspend_blockers;
> +static struct dentry *suspend_blocker_stats_dentry;
>
> #define pr_info_time(fmt, args...) \
> do { \
> @@ -54,6 +56,21 @@ static bool enable_suspend_blockers;
> tm.tm_hour, tm.tm_min, tm.tm_sec, ts.tv_nsec); \
> } while (0);
>
> +static int suspend_blocker_stats_show(struct seq_file *m, void *unused)
> +{
> + unsigned long irqflags;
> + struct suspend_blocker *blocker;
> +
> + seq_puts(m, "name\tactive\n");
> + spin_lock_irqsave(&list_lock, irqflags);
> + list_for_each_entry(blocker, &inactive_blockers, link)
> + seq_printf(m, "\"%s\"\t0\n", blocker->name);
> + list_for_each_entry(blocker, &active_blockers, link)
> + seq_printf(m, "\"%s\"\t1\n", blocker->name);
> + spin_unlock_irqrestore(&list_lock, irqflags);
> + return 0;
> +}
> +
> static void print_active_blockers_locked(void)
> {
> struct suspend_blocker *blocker;
> @@ -101,8 +118,8 @@ static DECLARE_WORK(suspend_work, suspend_worker);
> /**
> * suspend_blocker_init() - Initialize a suspend blocker
> * @blocker: The suspend blocker to initialize.
> - * @name: The name of the suspend blocker to show in debug messages.
> - *
> + * @name: The name of the suspend blocker to show in debug messages and
> + * /sys/kernel/debug/suspend_blockers.
> * The suspend blocker struct and name must not be freed before calling
> * suspend_blocker_destroy.
> */
> @@ -240,6 +257,19 @@ int request_suspend_state(suspend_state_t state)
> return 0;
> }
>
> +static int suspend_blocker_stats_open(struct inode *inode, struct file *file)
> +{
> + return single_open(file, suspend_blocker_stats_show, NULL);
> +}
> +
> +static const struct file_operations suspend_blocker_stats_fops = {
> + .owner = THIS_MODULE,
> + .open = suspend_blocker_stats_open,
> + .read = seq_read,
> + .llseek = seq_lseek,
> + .release = single_release,
> +};
> +
> static int __init suspend_block_init(void)
> {
> suspend_work_queue = create_singlethread_workqueue("suspend");
> @@ -251,4 +281,14 @@ static int __init suspend_block_init(void)
> return 0;
> }
>
> +static int __init suspend_block_postcore_init(void)
> +{
> + if (!suspend_work_queue)
> + return 0;
> + suspend_blocker_stats_dentry = debugfs_create_file("suspend_blockers",
> + S_IRUGO, NULL, NULL, &suspend_blocker_stats_fops);
> + return 0;
> +}
> +
> core_initcall(suspend_block_init);
> +postcore_initcall(suspend_block_postcore_init);
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists