Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <4520e86ead300c92de0736fcb7b1ec3045c34efa.camel@perches.com>
Subject: Re: [RFC PATCH v2 00/19] dynamic debug diet plan
From:   Joe Perches <joe@perches.com>
To:     Jim Cromie <jim.cromie@gmail.com>, jbaron@akamai.com,
        gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Date:   Tue, 29 Dec 2020 10:56:08 -0800
In-Reply-To: <20201225201944.3701590-1-jim.cromie@gmail.com>
References: <20201225201944.3701590-1-jim.cromie@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
User-Agent: Evolution 3.38.1-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 2020-12-25 at 13:19 -0700, Jim Cromie wrote:
> Well, we're mostly overeating, but we can all look forward to a diet
> in January.  And more exersize.
> 
> dyndbg's compiled-in data-table currently uses 56 bytes per prdebug;
> this includes 3 pointers to hierarchical "decorator" data, which is
> primarily for adding "module:function:line:" prefixes to prdebug
> messages, and for enabling and modifying those prdebugs selectively.
> 
> This patchset decouples "decorator" data, and makes it optional, and
> disposable.  By separating that data, it opens up possiblities to
> compress it, swap it out, map it selectively, etc.

While this may be somewhat useful, what debugging does it really help?
Are there really memory limited platforms that enable dynamic debug?