linux-kernel - Re: workqueue tracing removed?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMHCuPWjCTDvGihodaojU84q0LuFa6VYPBmS+DdeeX0XPdtOiw@mail.gmail.com>
Date:	Fri, 4 May 2012 23:22:43 +0530
From:	Sundar <sunder.svit@...il.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: workqueue tracing removed?

On Fri, May 4, 2012 at 10:39 PM, Tejun Heo <tj@...nel.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.
--
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/