From: fche@redhat.com (Frank Ch. Eigler)
To: kernelnewbies@lists.kernelnewbies.org
Subject: trace_console function definition not found in Linux kernel v3.5
Date: Fri, 28 Dec 2012 13:07:01 -0500 [thread overview]
Message-ID: <y0mhan6vynu.fsf@fche.csb> (raw)
In-Reply-To: <CANQLRiprYjJgErHkvgyaQPuY58PH7uO+5QUg+Q8_gJHpWG_1XA@mail.gmail.com> (siddharth goel's message of "Fri, 28 Dec 2012 13:13:01 +0530")
siddharth goel <siddharth98391@gmail.com> writes:
> In file kernel/printk.c in Linux Kernel 3.5 there is a function call
> trace_console(text, 0, len, len); @line 1219 .?
> But I could not find the definition for same. Am I missing any concept ?
This is a call to a tracepoint. Its definition is synthesized from
macros in <include/events/printk.h>. Calls to it may be monitored
with perf or systemtap.
- FChE
next prev parent reply other threads:[~2012-12-28 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 7:43 trace_console function definition not found in Linux kernel v3.5 siddharth goel
2012-12-28 18:07 ` Frank Ch. Eigler [this message]
2013-01-02 3:45 ` jiangtao.jit
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=y0mhan6vynu.fsf@fche.csb \
--to=fche@redhat.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).