From: wkevils@gmail.com (Kevin Wilson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Tracing - how can I know which method was called
Date: Mon, 18 Feb 2013 17:55:00 +0200 [thread overview]
Message-ID: <CAGXs5wV64WunFw5UJ=D=1uCzTgYAWgjCohy3t+Z5Tf_yvdoWtw@mail.gmail.com> (raw)
Hi,
I added a network event trace thus:
echo 1 > /sys/kernel/debug/tracing/events/net/net_dev_xmit/enable
Afterwards I see many lines with net_dev_xmit in /sys/kernel/debug/tracing.
Now, looking in the source code, I see that there are two calls to
trace_net_dev_xmit() in
dev_hard_start_xmit(). These invocations are identical.
see:
http://lxr.free-electrons.com/source/net/core/dev.c?v=2.6.37
Is there a way in which I can make the log say which of these
invocations was called ?
(without changing the dev_hard_start_xmit() method).
rgs,
Kevin
next reply other threads:[~2013-02-18 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 15:55 Kevin Wilson [this message]
2013-02-18 16:05 ` Tracing - how can I know which method was called Frederic Weisbecker
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='CAGXs5wV64WunFw5UJ=D=1uCzTgYAWgjCohy3t+Z5Tf_yvdoWtw@mail.gmail.com' \
--to=wkevils@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.