From: Joe Perches <joe@perches.com>
To: Jim Cromie <jim.cromie@gmail.com>,
jbaron@akamai.com, linux-kernel@vger.kernel.org
Cc: linux@rasmusvillemoes.dk, greg@kroah.com,
Arnd Bergmann <arnd@arndb.de>, Jessica Yu <jeyu@kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 04/16] dyndbg: rename __verbose section to __dyndbg
Date: Wed, 27 Nov 2019 12:42:12 -0800 [thread overview]
Message-ID: <80168e5bebedeb64e999ed11d8479846270bd3d7.camel@perches.com> (raw)
In-Reply-To: <20191127175051.1351346-1-jim.cromie@gmail.com>
On Wed, 2019-11-27 at 10:50 -0700, Jim Cromie wrote:
> dyndbg populates its callsite info into __verbose section, change that
> to a more specific and descriptive name, __dyndbg.
[]
> diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
[]
> @@ -1040,7 +1040,7 @@ static int __init dynamic_debug_init(void)
> ddebug_init_success = 1;
> vpr_info("%d modules, %d entries and %d bytes in ddebug tables, %d bytes in (readonly) verbose section\n",
This format should also change verbose to dyndbg
Maybe the ddebug word too
> modct, entries, (int)(modct * sizeof(struct ddebug_table)),
> - verbose_bytes + (int)(__stop___verbose - __start___verbose));
> + verbose_bytes + (int)(__stop___dyndbg - __start___dyndbg));
>
> /* apply ddebug_query boot param, dont unload tables on err */
> if (ddebug_setup_string[0] != '\0') {
next prev parent reply other threads:[~2019-11-27 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 17:50 Jim Cromie
2019-11-27 20:42 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-05 16:26 [PATCH 00/16] dynamic_debug: cleanups, 2 features Jim Cromie
2020-06-05 16:26 ` [PATCH 04/16] dyndbg: rename __verbose section to __dyndbg Jim Cromie
2019-10-29 20:00 Jim Cromie
2019-10-29 20:37 ` Rasmus Villemoes
2019-10-29 21:25 ` 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=80168e5bebedeb64e999ed11d8479846270bd3d7.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=jbaron@akamai.com \
--cc=jeyu@kernel.org \
--cc=jim.cromie@gmail.com \
--cc=linux-arch@vger.kernel.org \
--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®