Thanks!
On Thu, Jun 12, 2014 at 01:14:48AM +0200, Rafael J. Wysocki wrote: > On Wednesday, June 11, 2014 01:42:16 PM Todd E Brandt wrote: > > Is this accepted? > > Yes, applied. Thanks! > > > On Tue, Jun 10, 2014 at 11:41:33PM +0200, Rafael J. Wysocki wrote: > > > On Tuesday, June 10, 2014 05:17:16 PM Steven Rostedt wrote: > > > > On Tue, 10 Jun 2014 23:17:46 +0200 > > > > "Rafael J. Wysocki" <[email protected]> wrote: > > > > > > > > > On Tuesday, June 10, 2014 07:31:22 AM Todd E Brandt wrote: > > > > > > Adds two trace events which supply the same info that > > > > > > initcall_debug > > > > > > provides, but via ftrace instead of dmesg. The existing > > > > > > initcall_debug > > > > > > calls require the pm_print_times_enabled var to be set (either via > > > > > > sysfs or via the kernel cmd line). The new trace events provide all > > > > > > the > > > > > > same info as the initcall_debug prints but with less overhead, and > > > > > > also > > > > > > with coverage of device prepare and complete device callbacks. > > > > > > > > > > > > These events replace the device_pm_report_time event (which has been > > > > > > removed). device_pm_callback_start is called first and provides the > > > > > > device > > > > > > and callback info. device_pm_callback_end is called after with the > > > > > > device name and error info. The time and pid are gathered from the > > > > > > trace > > > > > > data headers. > > > > > > > > > > > > Signed-off-by: Todd Brandt <[email protected]> > > > > > > > > > > Steve needs to see this (CCed). > > > > > > > > The trace events look fine. Is there anything else you wanted me to > > > > look at? > > > > > > No, that's all, thanks! > > > > > > Rafael > > > > > -- > I speak only for myself. > Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
