introducing chuck silvers

[Chuck Silvers]

On Mon, Jun 11, 2012 at 08:32:12PM -0700, Chuck Silvers wrote:
> On Tue, May 29, 2012 at 02:38:24PM -0600, Justin T. Gibbs wrote:
> > PRs often (unfortunately) get lost.  If you can provide an enumeration of your
> > changes, I can introduce you to a committer that works in that area to help get
> > the changes into the tree.

oh, and a couple more:

 - the dtrace profile and lockstat providers both strip off too many
   stack frames from the stack() data on amd64, which makes it harder
   to see what's going on.  I'm not sure if this is always the case
   or if there are other interrupt paths with different stack behaviour.

 - sys/lockstat.h only defines the lockstat hooks as non-empty if
   KDTRACE_HOOKS is enabled, but nothing ensures that opt_kdtrace.h
   was previously included, and most of the .c files that include the
   various lock headers that include sys/lockstat.h don't previously
   include opt_kdtrace.h. thus, the inline versions of the various locks
   that are used in drivers are built into the base kernel mostly
   miss out on the lockstat hooks.

-Chuck