Marko Zec
0a705ab66f
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
2010-02-02 01:20:33 +00:00
2010-01-29 16:14:35 +00:00
2010-01-18 06:48:24 +00:00
2009-09-29 21:25:59 +00:00
2010-02-03 20:00:56 +00:00
2010-01-25 07:52:54 +00:00
2010-01-18 22:46:06 +00:00
2010-01-31 14:30:39 +00:00
2010-01-29 03:35:01 +00:00
2010-01-08 15:44:49 +00:00
2010-02-04 06:45:14 +00:00
2010-01-31 19:12:24 +00:00
2010-02-03 01:12:19 +00:00
2010-01-14 14:30:54 +00:00
2010-02-01 17:36:48 +00:00
2010-01-28 04:50:09 +00:00
2010-01-07 21:01:37 +00:00
2010-02-03 08:42:08 +00:00
2010-01-06 05:58:07 +00:00
2010-02-04 06:44:42 +00:00
2010-01-31 21:22:45 +00:00
2010-02-04 07:55:42 +00:00
2010-02-03 10:12:49 +00:00
2009-08-12 10:44:13 +00:00
2010-01-18 20:34:00 +00:00
2010-02-02 20:38:30 +00:00
2010-01-24 10:22:39 +00:00
2009-11-29 20:47:43 +00:00
2009-06-24 20:57:50 +00:00
2009-09-10 18:33:08 +00:00
2009-07-12 03:53:52 +00:00
2010-01-27 15:22:20 +00:00
2010-01-09 15:59:15 +00:00
2009-10-07 19:50:14 +00:00
2010-01-09 15:43:47 +00:00
2010-01-19 17:20:34 +00:00
2010-01-27 17:49:27 +00:00
2010-02-01 17:51:01 +00:00
2010-01-12 07:49:34 +00:00
2010-01-31 22:31:01 +00:00
2010-01-30 14:04:21 +00:00
2010-02-01 12:43:04 +00:00
2010-02-03 22:17:30 +00:00
2009-11-12 00:36:22 +00:00
2009-10-25 09:48:21 +00:00
2010-01-25 16:09:50 +00:00
2010-01-29 19:25:45 +00:00
2009-08-12 16:27:51 +00:00
2010-01-07 21:01:37 +00:00
0a705ab66f