From: vikram186@gmail.com (Vikram Narayanan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How vmlinux is recognized?
Date: Thu, 12 May 2011 09:02:30 +0530 [thread overview]
Message-ID: <BANLkTinG_rpCahAHKXp2_HmLF3J+DJQevQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTineK1CQrq4LZviWhp4aDhoPADkPaQ@mail.gmail.com>
On Thu, May 12, 2011 at 1:51 AM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> On Thu, May 12, 2011 at 03:11, Vikram Narayanan <vikram186@gmail.com> wrote:
>> Yes. I agree. But how who converts the ELF binary to raw binary so
>> that the processor understands. Or how is it actually done?
>
> OK I try my best to understand your question :)
>
> i think I got it...you probably guessed that vmlinux created first,
> then vmlinuz... AFAIK, it's the other way around...or more precisely,
> not both.
I think you got it wrong. I will try to put my question more elaborately.
1) The system is on and BIOS code runs. It gives the control to the
boot loader, say GRUB.
2) Grub picks up the kernel from the specific partition. (i.e a
vmlinuz image), which denotes that it is compressed.
3) There are uncompression routines in the kernel itself, If I am not
wrong. So the kernel uncompresses itself.
4) Now the uncompressed thing is the vmlinux image, right?
5) The vmlinux is in ELF format. Correct?
6) If the OS boots and if u try to run an ELF file, the loader knows
how to load that in the RAM. (I mean it knows how to interpret the ELF
format)
7) Coming back to the vmlinux image, Who takes care of the loading activity.?
8) Who recognizes that the image is ELF format and do the necessary
things accordingly.?
Hope I have my question clear now.
-
Thanks,
Vikram
next prev parent reply other threads:[~2011-05-12 3:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 18:06 How vmlinux is recognized? Vikram Narayanan
2011-05-11 19:17 ` Dave Hylands
2011-05-11 19:31 ` Vikram Narayanan
2011-05-11 19:45 ` Mulyadi Santosa
2011-05-11 20:04 ` Vikram Narayanan
2011-05-11 20:09 ` Mulyadi Santosa
2011-05-11 20:11 ` Vikram Narayanan
2011-05-11 20:21 ` Mulyadi Santosa
2011-05-12 3:32 ` Vikram Narayanan [this message]
2011-05-12 4:32 ` Sudheer Divakaran
2011-05-12 6:21 ` Sudheer Divakaran
2011-05-12 7:26 ` luca ellero
2011-05-12 8:17 ` Mulyadi Santosa
2011-05-13 0:19 ` Vikram Narayanan
2011-05-13 1:42 ` Dave Hylands
2011-05-16 3:14 ` Vikram Narayanan
2011-05-16 3:44 ` Peter Teoh
2011-05-16 14:12 ` Vikram Narayanan
2011-05-12 9:31 ` अनुज
2011-05-11 20:33 ` Manohar Vanga
2011-05-12 3:34 ` Vikram Narayanan
2011-05-12 16:46 ` mindentropy
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=BANLkTinG_rpCahAHKXp2_HmLF3J+DJQevQ@mail.gmail.com \
--to=vikram186@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).