* workqueue tracing removed?
@ 2012-05-02 10:06 Sundar
2012-05-03 20:54 ` Steven Rostedt
0 siblings, 1 reply; 6+ messages in thread
From: Sundar @ 2012-05-02 10:06 UTC (permalink / raw)
To: linux-kernel
Hi All,
The CONFIG_WORKQUEUE_TRACER has been removed by the commit
64166699752006f1a23a9cf7c96ae36654ccfc2c.
Any plans when this will be back?
Cheers!
--
---------
The views expressed in this email are personal and do not necessarily
echo my employers'.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: workqueue tracing removed?
2012-05-02 10:06 workqueue tracing removed? Sundar
@ 2012-05-03 20:54 ` Steven Rostedt
2012-05-04 17:06 ` Sundar
2012-05-04 17:09 ` Tejun Heo
0 siblings, 2 replies; 6+ messages in thread
From: Steven Rostedt @ 2012-05-03 20:54 UTC (permalink / raw)
To: Sundar; +Cc: linux-kernel, Frederic Weisbecker, Tejun Heo
Might get a better answer if you Cc'd the people involved.
-- Steve
On Wed, 2012-05-02 at 15:36 +0530, Sundar wrote:
> Hi All,
>
> The CONFIG_WORKQUEUE_TRACER has been removed by the commit
> 64166699752006f1a23a9cf7c96ae36654ccfc2c.
>
> Any plans when this will be back?
>
> Cheers!
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: workqueue tracing removed?
2012-05-03 20:54 ` Steven Rostedt
@ 2012-05-04 17:06 ` Sundar
2012-05-04 17:09 ` Tejun Heo
1 sibling, 0 replies; 6+ messages in thread
From: Sundar @ 2012-05-04 17:06 UTC (permalink / raw)
To: Steven Rostedt; +Cc: linux-kernel, Frederic Weisbecker, Tejun Heo
Ooops...very sorry I missed.
Thanks for the quick tip.
Cheers!
On Fri, May 4, 2012 at 2:24 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> Might get a better answer if you Cc'd the people involved.
>
> -- Steve
>
>
> On Wed, 2012-05-02 at 15:36 +0530, Sundar wrote:
>> Hi All,
>>
>> The CONFIG_WORKQUEUE_TRACER has been removed by the commit
>> 64166699752006f1a23a9cf7c96ae36654ccfc2c.
>>
>> Any plans when this will be back?
>>
>> Cheers!
>>
>
>
--
---------
The views expressed in this email are personal and do not necessarily
echo my employers.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: workqueue tracing removed?
2012-05-03 20:54 ` Steven Rostedt
2012-05-04 17:06 ` Sundar
@ 2012-05-04 17:09 ` Tejun Heo
2012-05-04 17:52 ` Sundar
1 sibling, 1 reply; 6+ messages in thread
From: Tejun Heo @ 2012-05-04 17:09 UTC (permalink / raw)
To: Steven Rostedt; +Cc: Sundar, linux-kernel, Frederic Weisbecker
Hello,
On Thu, May 03, 2012 at 04:54:14PM -0400, Steven Rostedt wrote:
> Might get a better answer if you Cc'd the people involved.
>
> On Wed, 2012-05-02 at 15:36 +0530, Sundar wrote:
> > Hi All,
> >
> > The CONFIG_WORKQUEUE_TRACER has been removed by the commit
> > 64166699752006f1a23a9cf7c96ae36654ccfc2c.
> >
> > Any plans when this will be back?
We do have tracepoints for work item queueing / execution but worker
tracing is still missing. What are you looking for?
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: workqueue tracing removed?
2012-05-04 17:09 ` Tejun Heo
@ 2012-05-04 17:52 ` Sundar
2012-05-04 17:55 ` Tejun Heo
0 siblings, 1 reply; 6+ messages in thread
From: Sundar @ 2012-05-04 17:52 UTC (permalink / raw)
To: Tejun Heo; +Cc: Steven Rostedt, linux-kernel, Frederic Weisbecker
On Fri, May 4, 2012 at 10:39 PM, Tejun Heo <tj@kernel.org> wrote:
> Hello,
>
> We do have tracepoints for work item queueing / execution but worker
> tracing is still missing. What are you looking for?
I can get the workqueue insertion/execution/end events; but in the
latest kernels, i see that worker:0/1 or worker:u/0 (similar) shows
prominently on the traces, but I am not able to exactly pin point
which worker thread was being executed; i remember on the older
kernels, it used to be visible as something like work_dbs (ondemand
governor) or work_*.
Am i missing something here?
Thanks
--
---------
The views expressed in this email are personal and do not necessarily
echo my employers.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: workqueue tracing removed?
2012-05-04 17:52 ` Sundar
@ 2012-05-04 17:55 ` Tejun Heo
0 siblings, 0 replies; 6+ messages in thread
From: Tejun Heo @ 2012-05-04 17:55 UTC (permalink / raw)
To: Sundar; +Cc: Steven Rostedt, linux-kernel, Frederic Weisbecker
On Fri, May 04, 2012 at 11:22:43PM +0530, Sundar wrote:
> I can get the workqueue insertion/execution/end events; but in the
> latest kernels, i see that worker:0/1 or worker:u/0 (similar) shows
> prominently on the traces, but I am not able to exactly pin point
> which worker thread was being executed; i remember on the older
> kernels, it used to be visible as something like work_dbs (ondemand
> governor) or work_*.
>
> Am i missing something here?
Workers are now shared, so all the workqueues share the same set of
workers. Work item execution can be tracked with tracepoints but
unfortunately there currently is no way to measure cpu consumption of
each work item.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-05-04 17:55 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-02 10:06 workqueue tracing removed? Sundar
2012-05-03 20:54 ` Steven Rostedt
2012-05-04 17:06 ` Sundar
2012-05-04 17:09 ` Tejun Heo
2012-05-04 17:52 ` Sundar
2012-05-04 17:55 ` Tejun Heo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox