dynamic_debug: allow multiple pending queries on boot-line

This patchset extends dynamic-debug facility to allow 
use of pr_debug() within a loadable module's module_init() 
function.  Query/rules can be given on the boot-line,
and are saved to a pending list if they cannot be applied
immediately.  Later, when the module is being loaded, the
pending list is scanned, and matching rules are applied.
Thus pr_debug() calls in the module's initialization function
are active when it is invoked.

Other features:
- dynamic_debug.verbose=1 at boot-time or while running
- ddebug_query can specify multiple queries, separated by ';'
- warn on multiple uses of a single match-spec in single query
- tolerate bad queries in ddebug_query w/o taking down facility

Possible additions (not done now)

- <dbgfs>/dynamic_debug/pending
  to show pending query/rules

- scan existing pending list before adding new entry
  currently same rule can be appended multiple times

- persistent queries
  when module is unloaded, applied rules are deleted


[PATCH 01/11] dynamic_debug: allow changing of dynamic_debug verbosity any time
[PATCH 02/11] dynamic_debug: trim source-path prefix from dynamic_debug/control
[PATCH 03/11] dynamic_debug: process multiple commands on a line
[PATCH 04/11] dynamic_debug: warn when >1 of each type of match-spec is given
[PATCH 05/11] dynamic_debug: use pr_info instead of printk(KERN_INFO ..
[PATCH 06/11] dynamic_debug: KERN_ERR should not depend upon verbosity
[PATCH 07/11] dynamic_debug: dont kill entire facility on error parsing ddebug_query
[PATCH 08/11] dynamic_debug: return int from ddebug_change
[PATCH 09/11] dynamic_debug: add_to_pending() saves non-matching queries for later.
[PATCH 10/11] dynamic_debug: call apply_pending_queries from ddebug_add_module
[PATCH 11/11] dynamic_debug: document use of pendinq queries at boot-time
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/