From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2488 invoked by alias); 1 Dec 2009 14:42:43 -0000 Received: (qmail 1774 invoked by uid 48); 1 Dec 2009 14:42:20 -0000 Date: Tue, 01 Dec 2009 14:42:00 -0000 Message-ID: <20091201144220.1771.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20091007205111.10745.jistone@redhat.com> References: <20091007205111.10745.jistone@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug tapsets/10745] Give access to "hidden" tracepoints X-Bugzilla-Reason: AssignedTo 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 X-SW-Source: 2009-q4/txt/msg00769.txt.bz2 ------- Additional Comments From fche at redhat dot com 2009-12-01 14:42 ------- (In reply to comment #0) > The only way I know to really discover *all* tracepoints is through debugfs on a > live kernel. That requirement doesn't really fit our general usage model. Maybe we don't have to be too dogmatic about our usual method. If we can eke out a list of tracepoints from a running kernel, and use its running build-id/release to validate it against the target -r kernel, then the information can probably be relied upon. (Of course, debugfs is sometimes not mounted.) -- http://sourceware.org/bugzilla/show_bug.cgi?id=10745 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.