Re: an online kernel crash book, and wondering what's deprecated
On Wed, Sep 26, 2012 at 8:11 PM, Mulyadi Santosa wrote: > Hi Rob... > > On Wed, Sep 26, 2012 at 6:33 PM, Robert P. J. Day > wrote: > > along those lines, i'm just digging into ftrace and was wondering if > > it in any way obsoleted systemtap, but i've heard from more than one > > source that while ftrace is allegedly more powerful, systemtap still > > has its place and is worth talking about. > > since systemtap is still included in Redhat Enterprise Linux, I could > firmly say SystemTap is still highly relevant these days. So is > kdump/kexec. > > > so ... if one was going to put together a (small) toolbox of kernel > > debugging tools, what's worth covering? interested in any feedback. > > IMHO, the most important part is the art of understanding oops message > and its related stack trace. > > I agree :) > Or worst, what if the system just hangsdivide and conquer things > like disabling acpi, sysrq, might be the skills we need here. > > Not sure if you agree with me here, but I just deliver my ideas. > > > > -- > regards, > > Mulyadi Santosa > Freelance Linux trainer and consultant > > blog: the-hydra.blogspot.com > training: mulyaditraining.blogspot.com > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > - Rohan ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: starting to patch kernel
Most of work in drivers is very HW or application specific and unfortunately is not suitable for up-streaming . A few of my experience I've converted to LDT - Linux Driver Template: https://github.com/makelinux/ldt/blob/master/README.md I would be very glad to receive your feedback. BTW, the code passed checkpatch.pl. Thank you! On Wed, Sep 26, 2012 at 10:37 PM, Greg Kroah-Hartman wrote: > On Wed, Sep 26, 2012 at 10:21:44PM +0200, Constantine Shulyupin wrote: >> Hi >> >> I am experienced embedded Linux driver developer. I have some spare >> time which I want to contribute to mainstream Linux kernel. > > How about working to get some of the drivers you have worked on upstream > properly? That would be a good task that you would know a lot about, > right? > > good luck, > > greg k-h -- Constantine Shulyupin http://www.MakeLinux.com/ Embedded Linux Systems, Device Drivers, TI DaVinci ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: starting to patch kernel
On Wed, Sep 26, 2012 at 4:21 PM, Constantine Shulyupin wrote: > Hi > > I am experienced embedded Linux driver developer. I have some spare > time which I want to contribute to mainstream Linux kernel. > Unfortunately http://kernelnewbies.org/KernelJanitors/Todo is very old. > Can you please suggest small tasks good for start? It can be code > clean up, API updates. > > Thank you > > -- > Constantine Shulyupin > http://www.MakeLinux.com/ > Embedded Linux Systems, > Device Drivers, TI DaVinci > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > You might want to ask Jeff Layton or Steve French (both CCed) about working on some code in the NFS tree. There's always a lot of stuff going on over there. The mailing list is somewhat active, too (at least for a file system mailing list). I don't know if that's anything you'd be interested in, but I like to lurk there among other places. -- Peace and Blessings, -Scott. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
starting to patch kernel
Hi I am experienced embedded Linux driver developer. I have some spare time which I want to contribute to mainstream Linux kernel. Unfortunately http://kernelnewbies.org/KernelJanitors/Todo is very old. Can you please suggest small tasks good for start? It can be code clean up, API updates. Thank you -- Constantine Shulyupin http://www.MakeLinux.com/ Embedded Linux Systems, Device Drivers, TI DaVinci ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Missing __versions section on .ko
On Mon, Sep 24, 2012 at 9:41 PM, Ramesh.P wrote: > Hi, > > Please see my comments inline. > > On Fri, Sep 21, 2012 at 2:39 PM, Pritam Bankar > wrote: >> Hi Ramesh thanks for great pdf. From whatever I understood after >> reading I fired command modinfo on my module and it gave output , >> >> vermagic: 3.2.0-23-generic-pae SMP mod_unload modversions 686 >> >> greping out vermagic. So I believe vermagic is behaving correctly. >> What is 686 in output ? > It represents the arch. the module is built for. In this case, it is 686. > >> Any other reason for missing __versions section ? > The other reason for invalid format is mismatch in arch. like mips vs > 686. It looks like you are trying to run this module on a 386 machine. > Can you confirm you have recompiled the module on the kernel you are > trying to link. > Yes I am running this module on i386 machine and I am linking compiled module on same kernel 3.2.0-23-generic-pae My module works perfectly on x86_64 machine which has same kernel 3.2.0-23-generic but without -pae >> >> On Wed, Sep 19, 2012 at 6:24 AM, Ramesh.P wrote: >>> Hi, >>> >>> 'Invalid module' is typically thrown when you don't compile your >>> module against the kernel you are linking into. I think __versions >>> section is added by vermagic.o as part of build process. Please refer >>> http://lwn.net/images/pdf/LDD3/ch02.pdf, Version dependency section >>> for more details. >>> >>> Thanks, >>> Ramesh >>> >>> On Tue, Sep 18, 2012 at 7:10 AM, Pritam Bankar >>> wrote: On Tue, Sep 18, 2012 at 7:27 PM, Pritam Bankar wrote: > Any idea what causes __versions section to get added in *.ko module. A > simple hello.ko on ubuntu 12.04 i386 machine gets loaded successfully. > Other module just doesn't get loaded giving error " Invalid module ". > When I compared both modules with objdump -h I found __versions > section was missing from second module and that can be the reason its > not getting loaded. How can I add this section to other .ko ? What > causes __versions to get added in ko ? I have compiled both modules with modpost and Module.symvers. Thanks, Pritam Bankar -- Pritam Bankar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies >> >> >> >> -- >> >> Pritam Bankar -- Pritam Bankar ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: getxattr field not initialized when trying to execute /init during boot
On Thu, Sep 13, 2012 at 5:08 PM, stl wrote: > > Hello all, > I am facing a problem when trying to boot linux 2.6.37 on a new architecture. > > At the end of the boot, it tries to launch /init by executing a sys_execve() > > Here is the what it does: > > sys_execve() > |-> do_execve() > |-> prepare_binprm() > |->security_bprm_set_creds() > |->cap_bprm_set_creds() > |->get_file_caps() >|->get_vfs_caps_from_disk() > > > In the get_vfs_caps_from_disk(), these is a verification to know if > inode->i_op->getxattr > has been initialized. > > In my case, it returns and error value, because this field is not initialized. > > So I am wondering by who and where this field is initialized? > And what is the aim of getxattr? > it is called extended attributes for filesystem: http://lwn.net/2000/1026/a/extended-attributes.php3 http://lwn.net/Articles/12060/ http://lwn.net/Articles/12061/ (there is a detail explanation in above link as I copied it here): +/* + * Extended attributes are stored on disk blocks allocated outside of + * any inode. The i_file_acl field is then made to point to this allocated + * block. If all extended attributes of an inode are identical, these + * inodes may share the same extended attribute block. Such situations + * are automatically detected by keeping a cache of recent attribute block + * numbers and hashes over the block's contents in memory. + * + * and for security modules: http://lwn.net/Articles/28223/ > Thanks in advance! > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -- Regards, Peter Teoh ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: I/O event notification mechanism - select() or epoll() ?
On Wed, Sep 26, 2012 at 7:49 PM, Rahul Bedarkar wrote: > Hi, > > I have to capture kernel udev events through libudev. One of API > provides asynchronous events by reading on file descriptor. I found > that there two ways to do that. > > 1) select call > I guessed when u called select() it will block, and so u can be very efficient - doing nothing until necessary, but also resource being used up - as the process is solely dedicated to listenting for event only. > 2) epoll > > good thing is u can parallel process other stuff at the same time, if after polling the replies from udev is not back yet. but the bad thing is response may not be so immediate, as u may be doing something else when the udev event comes in. > I also found that epoll is smarter and meant to replace old select call. > > What are your thoughts on these ? Which one is better ? > > Thanks > Rahul B. > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -- Regards, Peter Teoh ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
you might extend the "clean:" target to *really* clean the generated artifacts in that directory. or perhaps introduce "distclean:". rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
On Wed, Sep 26, 2012 at 10:21 PM, Constantine Shulyupin wrote: > I've made test script less noise. Please update sources. The driver > and the the test works with UART too. Hi... yup, less noise: sudo ./ldt-test stty: /dev/ttyS0: Input/output error No loopback on /dev/ttyS0 detected, running ldt driver with UART in loopback mode LDT nonblocking read/write test passed LDT blocking read/write test passed LDT mmap test passed LDT ioctl test passed trace_stat.log saved ftrace.log saved kernel.log saved -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
I've made test script less noise. Please update sources. The driver and the the test works with UART too. On Wed, Sep 26, 2012 at 5:04 PM, Robert P. J. Day wrote: > On Wed, 26 Sep 2012, Mulyadi Santosa wrote: > >> On Wed, Sep 26, 2012 at 6:03 PM, Constantine Shulyupin >> wrote: >> > Readme and sources: https://github.com/makelinux/ldt/blob/master/README.md >> > >> > To run driver with test script just run: >> > git clone git://github.com/makelinux/ldt.git && cd ldt && ./ldt-test >> > >> > You feedback, suggestions, discussions, recommendations patched will >> > be greatly appreciated! >> > >> >> Hi, >> >> I am the same person you probably see in LinkedIn :) >> >> Anyway, I use kernel 3.2.0-31-generic (Linux Mint 13) and when I run >> 'sudo ldt-test', I got: >> stty: /dev/ttyS0: Input/output error >> dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = >> output(dev, inbuf, data_in_len) >> No loopback on /dev/ttyS0 detected, running ldt driver with UART in >> loopback mode >> dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = >> output(dev, inbuf, data_in_len) >> >> is it due to I have no serial port? > > i get the same error on ubuntu 12.04, and it's pretty clearly > because my laptop has no actual serial port (something becoming more > and more common these days). i think you have to modify your examples > to consider that possibility. > > rday > > -- > > > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > -- Constantine Shulyupin http://www.MakeLinux.com/ Embedded Linux Systems, Device Drivers, TI DaVinci ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
Yes, it is because you have no serial port. In this case LDT emulates loopback. On Wed, Sep 26, 2012 at 4:48 PM, Mulyadi Santosa wrote: > On Wed, Sep 26, 2012 at 6:03 PM, Constantine Shulyupin > wrote: >> Readme and sources: https://github.com/makelinux/ldt/blob/master/README.md >> >> To run driver with test script just run: >> git clone git://github.com/makelinux/ldt.git && cd ldt && ./ldt-test >> >> You feedback, suggestions, discussions, recommendations patched will >> be greatly appreciated! >> > > Hi, > > I am the same person you probably see in LinkedIn :) > > Anyway, I use kernel 3.2.0-31-generic (Linux Mint 13) and when I run > 'sudo ldt-test', I got: > stty: /dev/ttyS0: Input/output error > dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = > output(dev, inbuf, data_in_len) > No loopback on /dev/ttyS0 detected, running ldt driver with UART in > loopback mode > dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = > output(dev, inbuf, data_in_len) > > is it due to I have no serial port? > > -- > regards, > > Mulyadi Santosa > Freelance Linux trainer and consultant > > blog: the-hydra.blogspot.com > training: mulyaditraining.blogspot.com -- Constantine Shulyupin http://www.MakeLinux.com/ Embedded Linux Systems, Device Drivers, TI DaVinci ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
On Wed, 26 Sep 2012, Mulyadi Santosa wrote: > On Wed, Sep 26, 2012 at 6:03 PM, Constantine Shulyupin > wrote: > > Readme and sources: https://github.com/makelinux/ldt/blob/master/README.md > > > > To run driver with test script just run: > > git clone git://github.com/makelinux/ldt.git && cd ldt && ./ldt-test > > > > You feedback, suggestions, discussions, recommendations patched will > > be greatly appreciated! > > > > Hi, > > I am the same person you probably see in LinkedIn :) > > Anyway, I use kernel 3.2.0-31-generic (Linux Mint 13) and when I run > 'sudo ldt-test', I got: > stty: /dev/ttyS0: Input/output error > dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = > output(dev, inbuf, data_in_len) > No loopback on /dev/ttyS0 detected, running ldt driver with UART in > loopback mode > dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = > output(dev, inbuf, data_in_len) > > is it due to I have no serial port? i get the same error on ubuntu 12.04, and it's pretty clearly because my laptop has no actual serial port (something becoming more and more common these days). i think you have to modify your examples to consider that possibility. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Why a locked page must be copied in COW?
Let me share my thoughts from what I have read elsewhere (same concepts
below applies to many other OS like Solaris too, where a lot of the memory
concepts comes from) - in general understanding the principles so that u
will not get lost in the codes...which can be buggy as well:
a.COW: the reason for this is to with efficiency and performance.
When u fork a process, the memory is shared between the parent and child
process, but when the parent or child start writing to the memory, the
sharing has to stop. so that's the reason for "copy on write". most of
the shared libraries are only for reading, so u can imagine the huge
saving, since multiple processes will be having a single physical copy of
library in memory.
b. Locking pages: generally, if both parent and child are sharing the
same page, then the page should have its write-protection enabled, so that
there is no need to duplicate the page, and there is assurance of reading
the page without fear of being modified.but if either party want to
write to it, then just make sure the page is first physically duplicated
into another page and then lock is removed, and now u have two unlocked
page accessible via two different process.
make sense? all those PTE stuff is just making sure that the page is
readable from its respective process, as different process have different
page table.
Just sidetracking a little, this concept is also applicable to filesystem.
On Sat, Sep 15, 2012 at 10:51 PM, Parmenides wrote:
> Hi,
>
> The do_wp_page() implements the Copy-On-write approach. I have no idea
> about its doing concerning locked pages.
>
> static int do_wp_page(struct mm_struct *mm, struct vm_area_struct * vma,
> unsigned long address, pte_t *page_table, pmd_t *pmd, pte_t pte)
> {
>
> old_page = pfn_to_page(pfn); <-- old_page is in quesiton.
>
> ... ... ...
>
> if (!TestSetPageLocked(old_page)) { <-- We test the 'PG_locked'
> flag of old_page.
>
> If it is not set, we can further check whether
>
> the page should be copied.
>
> int reuse = can_share_swap_page(old_page);
> unlock_page(old_page);
> if (reuse) { <-- If only
> one
> process owns old_page, we should copy it.
> flush_cache_page(vma, address);
> entry =
> maybe_mkwrite(pte_mkyoung(pte_mkdirty(pte)),
> vma);
> ptep_set_access_flags(vma, address, page_table,
> entry, 1);
> update_mmu_cache(vma, address, entry);
> pte_unmap(page_table);
> spin_unlock(&mm->page_table_lock);
> return VM_FAULT_MINOR;
> }
> }
> pte_unmap(page_table);
>
> /*
> * Ok, we need to copy. Oh, well..
> */ <-- At this
> point, we should copy old_page.
>
> ... ... ...
> }
>
> In conclusion, if old_page is locked or it is not locked and two or
> more processes own old_page, we should copy it. I don't understand
> why a locked page must be copied regardless of how many processes own
> it. Why do we give a locked page a special consideration?
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Regards,
Peter Teoh
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: LDT - Linux Driver Template
On Wed, Sep 26, 2012 at 6:03 PM, Constantine Shulyupin wrote: > Readme and sources: https://github.com/makelinux/ldt/blob/master/README.md > > To run driver with test script just run: > git clone git://github.com/makelinux/ldt.git && cd ldt && ./ldt-test > > You feedback, suggestions, discussions, recommendations patched will > be greatly appreciated! > Hi, I am the same person you probably see in LinkedIn :) Anyway, I use kernel 3.2.0-31-generic (Linux Mint 13) and when I run 'sudo ldt-test', I got: stty: /dev/ttyS0: Input/output error dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = output(dev, inbuf, data_in_len) No loopback on /dev/ttyS0 detected, running ldt driver with UART in loopback mode dio.c:138 io_start FAIL errno = 5 "Input/output error" -1 = ret = output(dev, inbuf, data_in_len) is it due to I have no serial port? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: an online kernel crash book, and wondering what's deprecated
Hi Rob... On Wed, Sep 26, 2012 at 6:33 PM, Robert P. J. Day wrote: > along those lines, i'm just digging into ftrace and was wondering if > it in any way obsoleted systemtap, but i've heard from more than one > source that while ftrace is allegedly more powerful, systemtap still > has its place and is worth talking about. since systemtap is still included in Redhat Enterprise Linux, I could firmly say SystemTap is still highly relevant these days. So is kdump/kexec. > so ... if one was going to put together a (small) toolbox of kernel > debugging tools, what's worth covering? interested in any feedback. IMHO, the most important part is the art of understanding oops message and its related stack trace. Or worst, what if the system just hangsdivide and conquer things like disabling acpi, sysrq, might be the skills we need here. Not sure if you agree with me here, but I just deliver my ideas. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
I/O event notification mechanism - select() or epoll() ?
Hi, I have to capture kernel udev events through libudev. One of API provides asynchronous events by reading on file descriptor. I found that there two ways to do that. 1) select call 2) epoll I also found that epoll is smarter and meant to replace old select call. What are your thoughts on these ? Which one is better ? Thanks Rahul B. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: an online kernel crash book, and wondering what's deprecated
On Wed, Sep 26, 2012 at 5:03 PM, Robert P. J. Day wrote: > > in my online travels yesterday, i ran across this gem, "Linux Kernel > Crash Book": > > http://www.dedoimedo.com/computers/crash-book.html > > and am now wondering about what would constitute a reasonable (and > minimal?) list of canonical kernel debugging tools. > > first, while the book above covers Linux Kernel Crash Dump (LKCD), > the author freely admits that it's been pretty much obsoleted by the > more recent and flexible kdump, so there seems to be little value in > digging into LKCD (or, in my case, adding any coverage of it to a > kernel debugging course, which i am currently designing). > > next, someone else's course i'm teaching next week has a kernel > debugging chapter which opens with netdump and diskdump before moving > onto kdump and kexec, but those earlier utilities are *also* > deprecated these days, > > > http://serverfault.com/questions/181554/how-should-i-capture-linux-kernel-panic-stack-traces > > so i would be tempted to skip any coverage of netdump and diskdump in > favour of additional and more advanced coverage of kdump and kexec. > > along those lines, i'm just digging into ftrace and was wondering if > it in any way obsoleted systemtap, but i've heard from more than one > source that while ftrace is allegedly more powerful, systemtap still > has its place and is worth talking about. > > so ... if one was going to put together a (small) toolbox of kernel > debugging tools, what's worth covering? interested in any feedback. > > rday > > -- > > > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > > > > > ___ > Kernelnewbies mailing list > Kernelnewbies@kernelnewbies.org > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > Hi Robert, Good to know that you are preparing material. For linux kernel debugging, I would love if you could include, kdb, kgdb and also their setup environment, like now most people do development on Virtual Machine. So the debugger needs to be setup on the VM and its serial port to the host machine, where the debugging logs would be displayed. - Rohan ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
an online kernel crash book, and wondering what's deprecated
in my online travels yesterday, i ran across this gem, "Linux Kernel Crash Book": http://www.dedoimedo.com/computers/crash-book.html and am now wondering about what would constitute a reasonable (and minimal?) list of canonical kernel debugging tools. first, while the book above covers Linux Kernel Crash Dump (LKCD), the author freely admits that it's been pretty much obsoleted by the more recent and flexible kdump, so there seems to be little value in digging into LKCD (or, in my case, adding any coverage of it to a kernel debugging course, which i am currently designing). next, someone else's course i'm teaching next week has a kernel debugging chapter which opens with netdump and diskdump before moving onto kdump and kexec, but those earlier utilities are *also* deprecated these days, http://serverfault.com/questions/181554/how-should-i-capture-linux-kernel-panic-stack-traces so i would be tempted to skip any coverage of netdump and diskdump in favour of additional and more advanced coverage of kdump and kexec. along those lines, i'm just digging into ftrace and was wondering if it in any way obsoleted systemtap, but i've heard from more than one source that while ftrace is allegedly more powerful, systemtap still has its place and is worth talking about. so ... if one was going to put together a (small) toolbox of kernel debugging tools, what's worth covering? interested in any feedback. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
LDT - Linux Driver Template
Hi I develop template of Linux driver. It can be used as sample for Linux driver development beginners and starting point for development of new drivers. The driver uses following Linux facilities: module, platform driver, file operations (read/write, mmap, ioctl, blocking and non-blocking mode, polling), kfifo, completion, interrupt, tasklet, work, kthread, timer, misc device, proc fs, UART 0x3f8, HW loopback, SW loopback Readme and sources: https://github.com/makelinux/ldt/blob/master/README.md To run driver with test script just run: git clone git://github.com/makelinux/ldt.git && cd ldt && ./ldt-test You feedback, suggestions, discussions, recommendations patched will be greatly appreciated! Thanks -- Constantine Shulyupin http://www.MakeLinux.com/ Embedded Linux Systems, Device Drivers, TI DaVinci ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
