From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-20007-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 26480 invoked by alias); 9 Oct 2012 19:45:06 -0000
Received: (qmail 26278 invoked by uid 48); 9 Oct 2012 19:44:51 -0000
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/14689] missing 'syscalls' tracepoints
Date: Tue, 09 Oct 2012 19:45:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: translator
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fche at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-14689-6586-SMt8A8j4er@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-14689-6586@http.sourceware.org/bugzilla/>
References: <bug-14689-6586@http.sourceware.org/bugzilla/>
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2012-q4/txt/msg00043.txt.bz2


http://sourceware.org/bugzilla/show_bug.cgi?id=14689

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> 2012-10-09 19:44:50 UTC ---
Note that stap does give access to the master tracepoints sys_enter and
sys_exit.  At one point, the demultiplexing done by the kernel for perf/ftrace
was such that there weren't really N low-level tracepoints that may be
individually turned on/off.  If any was turned on, the process incurred a
penalty for *every* syscall.  Demultiplexing was just a conditional
postprocessing phase, by which time the damage was already done.  It roughly
equivalent to

probe kernel.trace.sys_five = kernel.trace("sys_enter")
      { if ($syscall != 5) next; }

If this is still the case, then there is little point trying to connect to the
same demultiplexing widget.

See also bug #12748.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.