mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, linux-kernel@vger.kernel.org
Cc: linux@rasmusvillemoes.dk, greg@kroah.com,
	Jim Cromie <jim.cromie@gmail.com>
Subject: [PATCH 00/16] dynamic-debug cleanups, 2 new features
Date: Tue, 29 Oct 2019 13:59:48 -0600	[thread overview]
Message-ID: <20191029195948.9586-1-jim.cromie@gmail.com> (raw)

random cleanups of obsolete code, comments, verbose output, etc.

accept new query input:
  file inode.c:100-200
  file inode.c:start_*

add 'xyz' user flags to callsites' flagstate, allowing user to compose
a set of callsites by marking them with user flags.

extend flags-spec to allow filter-flags, which select callsites for
modification based upon their current flagstate.  This lets user
activate the set of callsites composed previously.

Jim Cromie (16):
  dyndbg: drop trim_prefix, obsoleted by __FILE__s relative path
  dyndbg: drop overwrought comment on ddebug_proc_open
  dyndbg: raise verbosity needed to enable ddebug_proc_* logging
  dyndbg: rename __verbose section to __dyndbg
  dyndbg: parse flags last, restore original behavior
  dyndbg: fix overcounting of ram used by dyndbg
  dyndbg: fix a BUG_ON in ddebug_change
  dyndbg: refactor parse_linerange out of ddebug_parse_query
  dyndbg: accept 'file foo.c:func1' and 'file foo.c:10-100'
  dyndbg: refactor ddebug_read_flags out of ddebug_parse_flags
  dyndbg: combine flags & mask into a struct, use that
  dyndbg: add filter parameter to ddebug_parse_flags
  dyndbg: extend ddebug_parse_flags to accept optional filter-flags
  dyndbg: prefer declarative init in caller, to memset in callee
  dyndbg: add inverted-flags, implement filtering on flags
  dyndbg: allow inverted-flag-chars in modflags

 .../admin-guide/dynamic-debug-howto.rst       |  72 +++--
 include/asm-generic/vmlinux.lds.h             |   6 +-
 include/linux/dynamic_debug.h                 |   7 +-
 kernel/module.c                               |   2 +-
 lib/dynamic_debug.c                           | 304 ++++++++++--------
 5 files changed, 236 insertions(+), 155 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-10-29 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 19:59 Jim Cromie [this message]
2019-11-27 17:49 Jim Cromie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191029195948.9586-1-jim.cromie@gmail.com \
    --to=jim.cromie@gmail.com \
    --cc=greg@kroah.com \
    --cc=jbaron@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®