On Monday 15 February 2010 6:21:40 am Shrikanth Kamath wrote:
> 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).
It is probably easier to do this with DTrace (albeit possibly with more
overhead). You can ktrace a kthread fine, but you would need to write your
own ktrace hooks (and record parser for kdump) which would take a bit longer
than a D script with DTrace.
--
John Baldwin
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
