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>,
saiprakash.ranjan@codeaurora.org
Subject: [PATCH 00/16] dynamic-debug cleanups, 2 new features
Date: Wed, 27 Nov 2019 10:49:29 -0700 [thread overview]
Message-ID: <20191127174929.1350995-1-jim.cromie@gmail.com> (raw)
this is v2 of patchset posted earlier:
https://lkml.org/lkml/2019/10/29/989
changes from v1:
dont drop trim_prefix yet, its harmless, and better supports old compilers.
dont move externs to header, despite checkpatch
New Features (review):
accept new query input:
file inode.c:100-200
file inode.c:start_*
add 'xyz' user flags, allowing user to compose an arbitrary set of
callsites by marking them with user flags. This takes 3 remaining
bits in the flags byte.
extend flags-spec to allow filter-flags, which select callsites for
modification based upon their current flags. This lets user activate
the set of callsites composed previously (xy+p).
cc: <saiprakash.ranjan@codeaurora.org>
Jim Cromie (16):
dyndbg-docs: eschew file /full/path query in docs
dyndbg: drop obsolete comment on ddebug_proc_open
dyndbg: raise verbosity needed to enable ddebug_proc_* logging
dyndbg: rename __verbose section to __dyndbg
dyndbg: fix overcounting of ram used by dyndbg
dyndbg: fix a BUG_ON in ddebug_describe_flags
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
dyndbg: make ddebug_tables list LIFO for add/remove_module
.../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 | 283 +++++++++++-------
5 files changed, 232 insertions(+), 138 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-27 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 17:49 Jim Cromie [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 19:59 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=20191127174929.1350995-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 \
--cc=saiprakash.ranjan@codeaurora.org \
/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®