From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 21:54:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CF5C16A41A for ; Fri, 21 Sep 2007 21:54:11 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.freebsd.org (Postfix) with ESMTP id 3869513C458 for ; Fri, 21 Sep 2007 21:54:11 +0000 (UTC) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 05F30732FF; Fri, 21 Sep 2007 21:57:10 +0000 (GMT) Date: Fri, 21 Sep 2007 21:57:09 +0000 From: John Birrell To: Doug Rabson Message-ID: <20070921215709.GA23720@what-creek.com> References: <6385B28C-01D1-459A-9543-E36C89C7F36E@xview.net> <20070920203413.GA13737@what-creek.com> <46F367E0.4000300@freebsd.org> <20070921070347.GA17990@what-creek.com> <1190360869.1627.9.camel@herring.rabson.org> <20070921081106.GA18488@what-creek.com> <1190362467.1627.13.camel@herring.rabson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1190362467.1627.13.camel@herring.rabson.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Dtrace port status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 21:54:11 -0000 On Fri, Sep 21, 2007 at 09:14:27AM +0100, Doug Rabson wrote: > I see your problem. How about adding a char td_dtrace_reserved[some > number] which can be cast into a dtrace structure in dtrace code but > which is opaque to normal kernel code? I am going to allocate the DTrace part like the scheduler stuff gets allocated - at the end using the uma zone calls. That way it will really be opaque. When the DTrace modules want to get at their private variables they can just offset the thread pointer. Unlike the td_sched, there won't be a pointer in the visible struct thread to retain binary compatibility with the release. -- John Birrell