From: Jon Masters <jonmasters@gmail.com>
To: krishna <krishna.c@globaledgesoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to understand flow of kernel code
Date: Sat, 4 Dec 2004 14:51:03 +0000 [thread overview]
Message-ID: <35fb2e590412040651196e9484@mail.gmail.com> (raw)
In-Reply-To: <41AE9E3E.9020307@globaledgesoft.com>
On Thu, 02 Dec 2004 10:16:54 +0530, krishna
<krishna.c@globaledgesoft.com> wrote:
> Can Anyone tell me the tips/tricks/techniques/practices followed in
> understanding flow of Linux kernel code?
A really good idea would be to visit:
* http://user-mode-linux.sourceforge.net/
Build a UML kernel with support for kernel debugging and follow their
instructions for debugging the kernel using gdb or even perhaps ddd.
Then you can watch the flow of initialisation for yourself within the
UML. Note that this obviously doesn't have low level hardware specifc
handling for your architecture, but it's a good place to start messing
around.
Also, the usual plugs:
* http://www.kernelnewbies.org/
* http://www.tech9.net/rml/kernel_book/
* http://www.xml.com/ldd/chapter/book/
* http://safari.oreilly.com/ - Read Understanding the Linux kernel online
Jon.
P.S. You're probably not in the UK, but the next issue of Linux User &
Developer will have a feature on UML debugging. My rather biased
opinion is that it'll be interesting to you :-)
next prev parent reply other threads:[~2004-12-04 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 4:46 How to understand flow of kernel code krishna
2004-12-02 6:21 ` Bernd Eckenfels
2004-12-02 16:11 ` Jeff V. Merkey
2004-12-04 12:55 ` [OT] " Andries Brouwer
2004-12-04 16:39 ` Manu Abraham
2004-12-04 14:51 ` Jon Masters [this message]
2004-12-27 20:22 ` David Eger
-- strict thread matches above, loose matches on Subject: below --
2004-12-02 18:28 Nick Warne
2004-12-02 19:13 ` Randy.Dunlap
2004-12-02 19:48 ` Cal Peake
2004-12-03 15:09 krishna
2004-12-03 15:27 ` Josh Boyer
2004-12-06 14:22 krishna
2004-12-06 18:49 ` Jon Masters
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=35fb2e590412040651196e9484@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=krishna.c@globaledgesoft.com \
--cc=linux-kernel@vger.kernel.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