kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Larry@GlueLogix.com (Larry Martin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question about pr_info (newbie)
Date: Tue, 30 Dec 2014 09:04:59 -0500	[thread overview]
Message-ID: <54A2B10B.2070303@GlueLogix.com> (raw)
In-Reply-To: <CAGXs5wVS2HTvwJfFvzFFSaS0mtHPgyz+1Yawz8UZsJeEmNyn9g@mail.gmail.com>

>

> I would appreciate if somebody can be more specific, how this can be
> done. I am using the defaults for syslog, which came with Fedora 21
> x86_64.
>

Kevin, I understand your frustration.  I think I used the wrong term.
It's not a "log level" thing, but a "dynamic debug" thing.  Dynamic 
Debug lets you turn on your specific message without seeing all other 
messages of the same "level."  But that means you may have to explicitly 
turn it off.

See:

google://pr_info
http://lwn.net/Articles/487437/
https://lwn.net/Articles/434833/

 From the last link:
> Turning on dynamic debug causes a new virtual file to appear at
> /sys/kernel/debug/dynamic_debug/control (modulo any individual
> preferences for the location of debugfs, naturally). Writing to that
> file will enable or disable specific debugging functions, as
> specified by a simple but flexible language.

> echo file tpm_nsc.c function init_nsc +p > .../dynamic_debug/control

So your incantation would be something like:

echo file myfile.c function init_me -p > mypath/dynamic_debug/control

LWN has a dynamic debug howto.  I assume it's in kernel docs too.

-- 
Larry Martin
www.GlueLogix.com
Design, Test and Support of Computerized Systems
desk USA 919.342.0201
cell USA 919.641.1733

  reply	other threads:[~2014-12-30 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1419872404.20373.kernelnewbies@kernelnewbies.org>
2014-12-29 17:11 ` question about pr_info (newbie) Larry Martin
2014-12-30 11:39   ` Kevin Wilson
2014-12-30 14:04     ` Larry Martin [this message]
2014-12-29  9:32 Kevin Wilson
2014-12-29 13:58 ` Valdis.Kletnieks at vt.edu

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=54A2B10B.2070303@GlueLogix.com \
    --to=larry@gluelogix.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).