From owner-freebsd-hackers@FreeBSD.ORG  Mon Feb 15 11:46:15 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id DD1ED106566B
	for <freebsd-hackers@freebsd.org>; Mon, 15 Feb 2010 11:46:15 +0000 (UTC)
	(envelope-from shrikanth07@gmail.com)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26])
	by mx1.freebsd.org (Postfix) with ESMTP id 993AB8FC0A
	for <freebsd-hackers@freebsd.org>; Mon, 15 Feb 2010 11:46:15 +0000 (UTC)
Received: by qw-out-2122.google.com with SMTP id 8so409042qwh.7
	for <freebsd-hackers@freebsd.org>; Mon, 15 Feb 2010 03:46:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:date:message-id:subject
	:from:to:content-type;
	bh=aq4Qr1D148yvMhrt6zw1kPK5E64rRpIKLYSvb6uaeTU=;
	b=vXgxFMCeEOmT3h+xL1gn0YOMOd9TE4TKPPCMHy10QjTrfhDG+a94Mw/rKL8/MADWgG
	RSekqzE8RH6WswsZXQvxGyHPtxd7pEWhE7xt/tdBcyHGZf5xW95ifW170Euz4zg+ttX4
	j8aHshbWo5M+pvftE3a7Z3jMJ1TBYj37Mh7jE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=uKVElLuZ6rzUzySDlrlBB/934GVxc18bf/Zl3GETycOmFNVQmb1G4C9aSeobIIMe8e
	xLyfrcwe+quUznQGA8uZ1FmAZ/lEPhprXk++OnX5sDjm2cqwNVrVDgFAoPu4drNhcrh1
	y09qcS7X35+0nBFUlwaxCmDNzTHYx4LJME0TY=
MIME-Version: 1.0
Received: by 10.229.20.77 with SMTP id e13mr2015226qcb.14.1266232900644; Mon, 
	15 Feb 2010 03:21:40 -0800 (PST)
Date: Mon, 15 Feb 2010 16:51:40 +0530
Message-ID: <291941b81002150321w7b0479beo1c6fec39ef6a7922@mail.gmail.com>
From: Shrikanth Kamath <shrikanth07@gmail.com>
To: freebsd-hackers@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: Ktrace'ing kernel threads
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 11:46:15 -0000

Can ktrace trace another kernel thread which has roughly the semantics as
below, right now it
does not hit any of the designated interesting points that ktrace is built
for, but what if I could define those,
will ktrace still allow tracing another kernel thread?

thread(client_info)
{
    ...
    ...
    build_msg(client_info);  /* this will malloc a mbuf and fill the data in
it */
    ...
    sosend(client_info);
}

I want to time the entry/return of build_msg, and the time sosend, dump
client_info (some specific fields).