[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1374188013.3356.7.camel@gandalf.local.home>
Date: Thu, 18 Jul 2013 18:53:33 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Shuah Khan <shuah.kh@...sung.com>
Cc: len.brown@...el.com, pavel@....cz, rjw@...k.pl,
gregkh@...uxfoundation.org, fweisbec@...il.com, mingo@...hat.com,
paul.gortmaker@...driver.com, joe@...ches.com,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
shuahkhan@...il.com
Subject: Re: [PATCH v5] power: new trace event to print device suspend and
resume time
On Thu, 2013-07-18 at 16:42 -0600, Shuah Khan wrote:
> +TRACE_EVENT(device_pm_report_time,
> +
> + TP_PROTO(struct device *dev, const char *pm_ops, s64 ops_time,
> + char *pm_event_str, int error),
> +
> + TP_ARGS(dev, pm_ops, ops_time, pm_event_str, error),
> +
> + TP_STRUCT__entry(
> + __string(device, dev_name(dev))
> + __string(driver, dev_driver_string(dev))
> + __string(parent, dev->parent ? dev_name(dev->parent) : "none")
> + __string(pm_ops, pm_ops ? pm_ops : "none ")
> + __string(pm_event_str, pm_event_str)
> + __field(s64, ops_time)
> + __field(int, error)
> + ),
> +
> + TP_fast_assign(
> + __assign_str(device, dev_name(dev));
> + __assign_str(driver, dev_driver_string(dev));
> + __assign_str(parent,
> + dev->parent ? dev_name(dev->parent) : "none");
Have you tried using the temp variables? These macros expand to be
called multiple times.
-- Steve
> + __assign_str(pm_ops, pm_ops ? pm_ops : "none ");
> + __assign_str(pm_event_str, pm_event_str);
> + __entry->ops_time = ops_time;
> + __entry->error = error;
> + ),
> +
> + /* ops_str has an extra space at the end */
> + TP_printk("%s %s parent=%s state=%s ops=%snsecs=%lld err=%d",
> + __get_str(driver), __get_str(device), __get_str(parent),
> + __get_str(pm_event_str), __get_str(pm_ops),
> + __entry->ops_time, __entry->error)
> +);
> +
> DECLARE_EVENT_CLASS(wakeup_source,
>
> TP_PROTO(const char *name, unsigned int state),
--
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