[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110810194529.GA5590@suse.de>
Date: Wed, 10 Aug 2011 12:45:29 -0700
From: Greg KH <gregkh@...e.de>
To: "Mansoor, Illyas" <illyas.mansoor@...el.com>
Cc: "Liu, ShuoX" <shuox.liu@...el.com>,
"linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>,
"Brown, Len" <len.brown@...el.com>,
"Yanmin_zhang@...ux.intel.com" <Yanmin_zhang@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] [PATCH v4] PM: add statistics debugfs file for
suspend to ram
On Wed, Aug 10, 2011 at 11:30:40PM +0530, Mansoor, Illyas wrote:
> > +struct suspend_stats suspend_stats;
> > static DEFINE_MUTEX(dpm_list_mtx);
> > static pm_message_t pm_transition;
> >
> > @@ -464,8 +465,12 @@ void dpm_resume_noirq(pm_message_t state)
> > mutex_unlock(&dpm_list_mtx);
> >
> > error = device_resume_noirq(dev, state);
> > - if (error)
> > + if (error) {
> > + suspend_stats.failed_resume_noirq++;
> > + dpm_save_failed_step(SUSPEND_RESUME_NOIRQ);
> > + dpm_save_failed_dev(dev_name(dev));
>
> Please make these statistics conditionally enabled, so on a production system
> If we need to disable these statistics code we should be able to do so.
Why, are they taking time or space that is needed for something else?
What's the downside here of just not always having this enabled?
greg k-h
--
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