Re: How to understand flow of kernel code

Re: How to understand flow of kernel code

[Nick Warne]

> Interesting trivia. Krishna in hindi means "all attractive". The Greeks 
> took the word and
> over time it was corrupted into the word "Christ" which was later used 
> for Jesus of Nazereth.
> I lot of people probably don't know his last name actually came from the 
>Vedic culture.

So I presume the 'Hare' bit came from that famous race with the tortoise...

JK'ing aside, good tips - I am trying to learn also to enable me to debug oops 
I get here and report properly back to the devs.

Nick
-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

Re: How to understand flow of kernel code

[Randy.Dunlap]

Nick Warne wrote:
>>Interesting trivia. Krishna in hindi means "all attractive". The Greeks 
>>took the word and
>>over time it was corrupted into the word "Christ" which was later used 
>>for Jesus of Nazereth.
>>I lot of people probably don't know his last name actually came from the 
>>Vedic culture.
> 
> 
> So I presume the 'Hare' bit came from that famous race with the tortoise...
> 
> JK'ing aside, good tips - I am trying to learn also to enable me to debug oops 
> I get here and report properly back to the devs.

Besides reading the code, Denis Vlasenko 
<vda@port.imtp.ilyichevsk.odessa.ua> has written & posted:
Subject: [RFC] HOWTO find oops location, v2
on 2004.Aug.15.  Find it in an lkml email archive.

-- 
~Randy

Re: How to understand flow of kernel code

[Cal Peake]

On Thu, 2 Dec 2004, Randy.Dunlap wrote:

> Besides reading the code, Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
> has written & posted:
> Subject: [RFC] HOWTO find oops location, v2
> on 2004.Aug.15.  Find it in an lkml email archive.

Another good reference is this slideshow by Simon Trimer:

  http://www.urbanmyth.org/linux/oops/

  http://www.urbanmyth.org/linux/oops/slides.html


-- Cal

How to understand flow of kernel code

[krishna]

Hi jon,

Thank you. I am able to use UML.

Regards,
Krishna Chaitanya

Re: How to understand flow of kernel code

[Jon Masters]

krishna wrote:

> Thank you. I am able to use UML.

This needs to be advocated more profusely as a experimentation mechanism 
suitable for people just wanting to have an overview initially.

Sure, it's not great for figuring out the lower level stuff, but it 
shines if you want to pick apart the overall VM or sched stuff.

Cheers,

Jon.

How to understand flow of kernel code

[krishna]

Hi Elladan,

    Thank you very much.
    Can u tell me how can I start from an interrupt.

Regards,
Krishna Chaitanya

Elladan wrote:

It's written in C, so it should be quite simple.

Most everything starts from a syscall, or an interrupt.  

-J

On Thu, Dec 02, 2004 at 10:16:54AM +0530, krishna wrote:
  

Hi,

Can Anyone tell me the tips/tricks/techniques/practices followed in 
understanding flow of Linux kernel code?

Regards,
Krishna Chaitanya

Re: How to understand flow of kernel code

[Josh Boyer]

On Fri, 2004-12-03 at 09:09, krishna wrote:
> Hi Elladan,
> 
>     Thank you very much.
>     Can u tell me how can I start from an interrupt.

Look for the do_IRQ function.  Figure out how it's called, then figure
out what it does, and then figure out how the system is restored.  And
it's a bit more than just C code, so you'll need some understanding of
assembly for whichever architecture you're interested in.

Good luck.

josh

How to understand flow of kernel code

[krishna]

Hi,

Can Anyone tell me the tips/tricks/techniques/practices followed in 
understanding flow of Linux kernel code?

Regards,
Krishna Chaitanya

Re: How to understand flow of kernel code

[Bernd Eckenfels]

In article <41AE9E3E.9020307@globaledgesoft.com> you wrote:
> Can Anyone tell me the tips/tricks/techniques/practices followed in 
> understanding flow of Linux kernel code?

You read the code and use an ide which allows to find declarations/usage
(ctags suppot in editor for eample). You could also browse with LXR. But
some basic architectural understanding from various kernel books and
articles is helpfull.

http://lxr.linux.no/source/init/main.c

Greetings
Bernd

Re: How to understand flow of kernel code

[Jeff V. Merkey]

Hare Krishna, Hare Krishna, Krishna, Krishna, Hare, Hare,
Hare Rama, Hare Rama, Rama, Rama, Hare, Hare.

Start at entry.S and head.S in /arch/i386/kernel and trace the 
initialization. It's a good place
to start for understanding how the kernel boots and follow the code 
through init. Check out
the userspace interaction as well. It will at least start you with the 
basics.

You may want to offer a leaf, fruit, flower, and water to Lord Chaitanya 
and Lord Krishna
and chant the mantras in between to ask for guidance and understanding 
(I'm serious).

Interesting trivia. Krishna in hindi means "all attractive". The Greeks 
took the word and
over time it was corrupted into the word "Christ" which was later used 
for Jesus of Nazereth.
I lot of people probably don't know his last name actually came from the 
Vedic culture.

Hare Krishna,

Jeff

krishna wrote:

> Hi,
>
> Can Anyone tell me the tips/tricks/techniques/practices followed in 
> understanding flow of Linux kernel code?
>
> Regards,
> Krishna Chaitanya
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

Re: How to understand flow of kernel code

[Manu Abraham]

On Thu December 2 2004 8:11 pm, Jeff V. Merkey wrote:
> Hare Krishna, Hare Krishna, Krishna, Krishna, Hare, Hare,
> Hare Rama, Hare Rama, Rama, Rama, Hare, Hare.
>
> Start at entry.S and head.S in /arch/i386/kernel and trace the
> initialization. It's a good place
> to start for understanding how the kernel boots and follow the code
> through init. Check out
> the userspace interaction as well. It will at least start you with the
> basics.
>
> You may want to offer a leaf, fruit, flower, and water to Lord Chaitanya
> and Lord Krishna
> and chant the mantras in between to ask for guidance and understanding
> (I'm serious).
>
> Interesting trivia. Krishna in hindi means "all attractive". The Greeks
> took the word and
> over time it was corrupted into the word "Christ" which was later used
> for Jesus of Nazereth.
> I lot of people probably don't know his last name actually came from the
> Vedic culture.

FYI, The vedic culture refers to vedic era.

The Vedic scriptures were written much before the books Mahabharatha and 
Ramayana.
	
The last of the vedas, ie, i don't know whether it is the Rig veda or the 
Yajur veda, talks about Kristu or Kristo somebody like that, referring to 
Jesus of Nazareth.

Maybe you should consult some Sanskrit scholars, before making wrong 
statements.

Manu 
>
> Hare Krishna,
>
> Jeff
>
> krishna wrote:
> > Hi,
> >
> > Can Anyone tell me the tips/tricks/techniques/practices followed in
> > understanding flow of Linux kernel code?
> >
> > Regards,
> > Krishna Chaitanya
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: How to understand flow of kernel code

[Jon Masters]

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 :-)

Re: How to understand flow of kernel code

[David Eger]

One of the more bizarre details of kernel initialization is in
do_initcalls().  It's one of the last things in the initialization
sequence that you see code for, and it does some odd function-pointer
table assembly hackery.  You don't actually see a list of the functions
that do_initcalls() calls because *it's generated at compile time*.
Each module/filesystem/arch/etc can register an initialization function
with the build system through a declaration like the following in
"binfmt_elf.c":

core_initcall(init_elf_binfmt);

This macro is defined in init.h, along with several others:

#define core_initcall(fn)               __define_initcall("1",fn)
#define postcore_initcall(fn)           __define_initcall("2",fn)
#define arch_initcall(fn)               __define_initcall("3",fn)
#define subsys_initcall(fn)             __define_initcall("4",fn)
#define fs_initcall(fn)                 __define_initcall("5",fn)
#define device_initcall(fn)             __define_initcall("6",fn)
#define late_initcall(fn)               __define_initcall("7",fn)

When the build system is done building all the files, it gathers together
all of the special initcall declarations and links them into one table:
the one that do_initcalls() iterates over.

-dte