From: ebiederm@xmission.com (Eric W. Biederman)
To: Gerd Hoffmann <kraxel@suse.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix ELF entry point (i386)
Date: Sun, 05 Mar 2006 09:34:18 -0700 [thread overview]
Message-ID: <m1bqwkc0l1.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <43FC4682.6050803@suse.de> (Gerd Hoffmann's message of "Wed, 22 Feb 2006 12:09:54 +0100")
Gerd Hoffmann <kraxel@suse.de> writes:
> Hi,
>
> Elf entry point is virtual address, not physical ...
>
> please apply,
NACK
We load the kernel at physical addresses and we enter
the kernel at a physical address. Even the entry point
expects that.
Is there some reason you think the entry point is virtual?
Eric
next prev parent reply other threads:[~2006-03-05 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 11:09 [PATCH] Fix ELF entry point (i386) Gerd Hoffmann
2006-03-05 16:34 ` Eric W. Biederman [this message]
2006-03-06 13:16 ` Gerd Hoffmann
2006-03-06 19:11 ` Eric W. Biederman
2006-03-07 13:41 ` Gerd Hoffmann
2006-03-07 17:55 ` Eric W. Biederman
2006-03-10 9:58 ` Gerd Hoffmann
2006-05-11 13:05 ` Gerd Hoffmann
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=m1bqwkc0l1.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=kraxel@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).