From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How vmlinux is recognized?
Date: Wed, 11 May 2011 12:17:54 -0700 [thread overview]
Message-ID: <BANLkTinpi3jqa3=VCP-2B9Az6Y3GjO2K7Q@mail.gmail.com> (raw)
In-Reply-To: <1305137213.2347.12.camel@ubuntu.ubuntu-domain>
Hi Vikram,
On Wed, May 11, 2011 at 11:06 AM, Vikram Narayanan <vikram186@gmail.com> wrote:
> Hi,
>
> Sorry if this question is stupid.
> How the vmlinux (an ELF executable) is recognized by the processor?
> What are the files that are responsible for this?
Well the short answer is that it isn't.
The ELF file is normally just one stage of the process. You still need
to extract a binary from the ELF, and the binary contains the raw
executable code that the processor uses.
Normally the boot loader will extract a binary (perhaps from an ELF,
or perhaps from a raw binary image) and this is what the processor
sees.
--
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com
next prev parent reply other threads:[~2011-05-11 19:17 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 [this message]
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
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='BANLkTinpi3jqa3=VCP-2B9Az6Y3GjO2K7Q@mail.gmail.com' \
--to=dhylands@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).