zec 393450ca7b Instead of spamming the console on each curvnet recursion event, print
out each such call graph only once, along with a stack backtrace.  This
should make kernels built with VNET_DEBUG reasonably usable again in
busy / production environments.

Introduce a new DDB command "show vnetrcrs" which dumps the whole log
of distinctive curvnet recursion events.  This might be useful when
recursion reports get burried / lost too deep in the message buffer.
In the later case stack backtraces are not available.

Reviewed by:	bz
MFC after:	3 days
2010-02-04 07:55:42 +00:00
..
2009-04-02 13:02:12 +00:00
2007-12-09 20:47:12 +00:00
2008-03-17 01:26:44 +00:00
2010-01-10 12:03:53 +00:00
2009-04-14 23:05:36 +00:00