From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23979 invoked by alias); 4 Aug 2014 16:20:28 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 23908 invoked by uid 48); 4 Aug 2014 16:20:22 -0000 From: "dsmith at redhat dot com" To: systemtap@sourceware.org Subject: [Bug tapsets/6525] need utrace task-finder-based pid->execname, pid->cwd-path-name tables Date: Mon, 04 Aug 2014 16:20:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dsmith at redhat dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q3/txt/msg00121.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=6525 --- Comment #13 from David Smith --- (In reply to Frank Ch. Eigler from comment #12) > David, I think the old idea was to introduce some tapset functions that, > based on kprocess.* probes or the like, maintain global data like pid2FOO > tables for use by stap. The idea was not to -read- /proc/$PID/foo, but to > track some equivalent data within stap globals. Yes, that was the old idea. I thought Martin was proposing a new idea of reading /proc/$PID/foo. With enough work, we could probably maintain some global data that mapped pids to execnames. The unfortunate part would be that it would have to map every single process in the system in order to be able to give you any pid. Mapping pids to cwd paths would be harder, since we don't keep up with that now. The trickiest part of all of this would be finding storage for all this new information, especially paths. -- You are receiving this mail because: You are the assignee for the bug.