From: Frank Rowand <frank_rowand@hp.com>
To: Paul Bame <bame@debian.fc.hp.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Helge.Deller@ruhr-uni-bochum.de, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] hack to use HPUX boot loader
Date: Thu, 28 Oct 1999 14:02:48 -0700 [thread overview]
Message-ID: <3818B9F8.E38FFEA7@hp.com> (raw)
In-Reply-To: 199910281838.MAA20701@debian.fc.hp.com
Paul Bame wrote:
>
> = >
> = > > I find it very strange that the kernel is being linked to start at
> = > > 0xc0010000. It's not your average machine that has this much physical
> = >
> = > Logical or physical ?
> =
> = Physical, at least when loading with hpux. LDFLAGS are "-R 0xc0010000
> = -N -e stext". I know at one time the link was being done at 0x10000.
>
> There isn't any concept of physical versus virtual
> location in the HP linker that I'm aware of, though there might be somthing
> hidden in an extension record.
>
> The hpux boot loader assumes the text relocation address should also be
> used as a physical load address. In the case of Linux, relocated
> at 3Gb, this clearly makes no sense. It works fine for HP-UX which
> is relocated to, and runs in, low physical memory.
>
> = Does anyone know why this was changed?
>
> I assume the earlier linking was purely experimental, since I've been
> told (and haven't confirmed myself) that Linux 2.2.x essentially needs
> to be relocated at 3Gb (or some other big value) because it assumes
> it's available from the page tables of every process. If
> Linux was relocated at addresses near zero, this would result in
> user programs having to start at addresses larger than the amount
> of memory used by the kernel, which would be weird.
>
> -P
Not so weird. It's just a virtual address, not a physical address.
-Frank
prev parent reply other threads:[~1999-10-28 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-22 22:34 [parisc-linux] hack to use HPUX boot loader Paul Bame
1999-10-24 23:08 ` Alex deVries
1999-10-26 14:50 ` Paul Bame
1999-10-26 23:41 ` John David Anglin
1999-10-27 17:11 ` Paul Bame
1999-10-27 22:02 ` Helge Deller
1999-10-28 15:22 ` John David Anglin
1999-10-28 14:40 ` Paul Bame
1999-10-28 16:18 ` Alan Cox
1999-10-28 17:03 ` John David Anglin
1999-10-28 17:18 ` [parisc-linux] bios passwd override procedure ? Ed June
1999-10-28 17:38 ` [parisc-linux] hack to use HPUX boot loader Paul Bame
1999-10-28 20:26 ` Philippe Benard
1999-10-28 20:45 ` John David Anglin
1999-10-28 21:10 ` Philippe Benard
1999-10-28 20:11 ` Paul Bame
1999-10-28 20:34 ` John David Anglin
1999-10-28 21:02 ` Frank Rowand [this message]
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=3818B9F8.E38FFEA7@hp.com \
--to=frank_rowand@hp.com \
--cc=Helge.Deller@ruhr-uni-bochum.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bame@debian.fc.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=frowand@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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