Hi, Saket, Thanks for the tip!
*--*Airton Ishimori On Tue, May 19, 2015 at 2:53 AM, Saket Sinha <saket.sinh...@gmail.com> wrote: > HI , > > If you want to go further than just the printks, you can setup a > qemu setup and attach gdb to it. > Then you can even set breakpoints to analyze it. > > Let me know if you have any issues with the setup. > > Regards, > Saket Sinha > > > On Tue, May 19, 2015 at 11:18 AM, anish singh > <anish198519851...@gmail.com> wrote: > > > > > > On Mon, May 18, 2015 at 12:23 PM, Airton Ishimori < > nobumasa....@gmail.com> > > wrote: > >> > >> 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? > > > > > > There are only two reasons why your printk is not coming > > 1. Your printk is not executing. > > 2. Your driver is not getting installed. > > Have you verified both of these points? > >> > >> > >> Thanks in advance, > >> > >> -- > >> Airton Ishimori > >> > >> > >> _______________________________________________ > >> Kernelnewbies mailing list > >> Kernelnewbies@kernelnewbies.org > >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > >> > > > > > > _______________________________________________ > > Kernelnewbies mailing list > > Kernelnewbies@kernelnewbies.org > > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > >
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies