All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: todd.e.brandt@linux.intel.com, linux-pm@vger.kernel.org,
	rafael.j.wysocki@intel.com
Subject: Re: [PATCH] PM: trace events for suspend/resume
Date: Fri, 23 May 2014 01:06:32 +0200	[thread overview]
Message-ID: <1707167.dvsBe2mo72@vostro.rjw.lan> (raw)
In-Reply-To: <1400798505.26671.9.camel@pippen.local.home>

On Thursday, May 22, 2014 06:41:45 PM Steven Rostedt wrote:
> On Thu, 2014-05-22 at 10:07 -0700, Todd E Brandt wrote:
> >  
> > > >  #include <asm/io.h>
> > > >  #include <asm/uaccess.h>
> > > > @@ -835,7 +836,9 @@ acpi_status acpi_os_remove_interrupt_handler(u32 irq, acpi_osd_handler handler)
> > > >  
> > > >  void acpi_os_sleep(u64 ms)
> > > >  {
> > > > +	trace_suspend_resume("acpi_os_sleep", true);
> > > >  	msleep(ms);
> > > > +	trace_suspend_resume("acpi_os_sleep", false);
> > > >  }
> > > 
> > > This function doesn't have anything to do with system suspend/resume.
> > > It is for waiting. :-)
> > 
> > Yea but it really helps you diagnose bad firmware during suspend/resume
> > (for instance when there's just an arbitrary sleep 100ms in the ACPI code).
> > But it doesn't matter for general performance testing, I'll remove it on v2
> > submit.
> > 
> > > 
> > > The rest of the patch looks OK to me.
> > > 
> > > Steven, what about the tracing angle?
> 
> It should be under an ACPI system (if there is one). Looks rather silly
> to call it for suspend.

I meant the rest of the patch, not this particular hunk. :-)

Rafael


  reply	other threads:[~2014-05-22 22:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 23:02 [PATCH] PM: trace events for suspend/resume Todd E Brandt
2014-05-22  0:01 ` Rafael J. Wysocki
2014-05-22 17:07   ` Todd E Brandt
2014-05-22 22:41     ` Steven Rostedt
2014-05-22 23:06       ` Rafael J. Wysocki [this message]
2014-05-30 14:49         ` Todd E Brandt
2014-05-22 22:16   ` Srivatsa S. Bhat
2014-05-22 22:44     ` Steven Rostedt
2014-05-23  6:36       ` Srivatsa S. Bhat
2014-05-22 23:50     ` Todd E Brandt
2014-05-23  6:37       ` Srivatsa S. Bhat

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=1707167.dvsBe2mo72@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=todd.e.brandt@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.