Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753899Ab2EDRzp (ORCPT ); Fri, 4 May 2012 13:55:45 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:35878 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753029Ab2EDRzo (ORCPT ); Fri, 4 May 2012 13:55:44 -0400 Date: Fri, 4 May 2012 10:55:40 -0700 From: Tejun Heo To: Sundar Cc: Steven Rostedt , linux-kernel@vger.kernel.org, Frederic Weisbecker Subject: Re: workqueue tracing removed? Message-ID: <20120504175540.GG24639@google.com> References: <1336078454.14207.105.camel@gandalf.stny.rr.com> <20120504170948.GE24639@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 942 Lines: 24 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/