From: nobumasa.bcc@gmail.com (Airton Ishimori)
To: kernelnewbies@lists.kernelnewbies.org
Subject: A flow path for ethernet kernel driver
Date: Mon, 18 May 2015 16:23:15 -0300 [thread overview]
Message-ID: <CAHVg_i6KtzMKBaWJyuxe=vjqMRWky+w03ADYEMCdfcMQrMt8Mg@mail.gmail.com> (raw)
Hello, everybody,
I'm trying to develop a new Ethernet driver (Realtek) for Linux kernel
4.0.2.
[ 3.612938] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
As part of my studies, I'm trying to trace the path for functions defined
in drivers/net/ethernet/realtek/r8169.c, net/core/dev.c and
net/core/dev_ioctl.c. I'm using "printks" for this purpose. For instance,
something like:
printk("TEST: __dev_set_promiscuity\n");
However, I'm not getting what's going on. I can set/unset the promiscuity
behaviour via ifconfig command.
[ 131.330091] device eth0 entered promiscuous mode
[ 170.619086] device eth0 left promiscuous mode
By looking at the dmesg output above, I thought the function that deals
with promiscuity was __dev_set_promiscuity() defined in net/core/dev.c, because
this function calls a function to print the message above:
pr_info("device %s %s promiscuous mode\n", dev->name, dev->flags &
IFF_PROMISC ? "entered" : "left");
But, when I tried to look for my printk message with dmesg after compiling
and running the kernel, I couldn't find it.
$ cd linux-4.0.2/
$ make net && make modules
$ sudo make modules_install && sudo make install
Can somebody help me to understand what's happening?
Thanks in advance,
*--*Airton Ishimori
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150518/9667cdfe/attachment.html
next reply other threads:[~2015-05-18 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 19:23 Airton Ishimori [this message]
2015-05-18 20:01 ` A flow path for ethernet kernel driver Rami Rosen
2015-05-18 23:11 ` Airton Ishimori
2015-05-19 5:48 ` anish singh
2015-05-19 5:53 ` Saket Sinha
2015-05-19 14:09 ` Airton Ishimori
2015-05-19 14:08 ` Airton Ishimori
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='CAHVg_i6KtzMKBaWJyuxe=vjqMRWky+w03ADYEMCdfcMQrMt8Mg@mail.gmail.com' \
--to=nobumasa.bcc@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.