Date: Fri, 21 Apr 2006 07:09:31 GMT From: John Birrell <jb@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 95767 for review Message-ID: <200604210709.k3L79V8K043477@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=95767 Change 95767 by jb@jb_freebsd2 on 2006/04/21 07:09:28 Add (some? of) the extra variables that DTrace needs in struct proc. It likes to get up close and personal with it's buddies. Adding fields like this raises the issue of how Sun's CDDL applies in this case. Should I expect to get permission to do this and retain the BSD license. Without that permission, I can't see how doing this is legal. And looking at the OpenSolaris distribution and seeing AT&T copyright references, I can't help but wonder what a certain company in the US south would think about this. Perhaps I should just hope they go belly up first. 8-) Affected files ... .. //depot/projects/dtrace/src/sys/sys/proc.h#2 edit Differences ... ==== //depot/projects/dtrace/src/sys/sys/proc.h#2 (text+ko) ==== @@ -620,6 +620,9 @@ STAILQ_HEAD(, ktr_request) p_ktr; /* (o) KTR event queue. */ LIST_HEAD(, mqueue_notifier) p_mqnotifier; /* (c) mqueue notifiers.*/ struct auditinfo *p_au; /* (c) Process audit properties. */ + int p_dtrace_probes; /* (c) Are there probes for this proc? */ + u_int64_t p_dtrace_count; /* (c) Number of DTrace tracepoints */ + void *p_dtrace_helpers; /* (c) DTrace helpers, if any */ }; #define p_session p_pgrp->pg_session
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604210709.k3L79V8K043477>