From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] ia64 compressed makefile target
Date: Wed, 23 Oct 2002 20:43:51 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805217@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805211@msgid-missing>
>>>>> On Wed, 23 Oct 2002 10:46:32 -0700, "Luck, Tony" <tony.luck@intel.com>
said:
Tony> Or perhaps David will take the CONFIG_IA64_VMAP_KERNEL patch
Tony> that I posted a week ago which also allows the kernel to run
Tony> on systems without memory at the default link address.
Tony> Admittedly it's more than one line, but it contains much of
Tony> the same infrastructure that is needed to support kernel text
Tony> replication.
> I don't have a strong preference either way, but I do have some
> concerns about the VMAP_KERNEL. I really dislike the fact that it
> requires different versions of virtual-to-physical translations for
> kernel addresses. No other platform does that, so it will be a source
> of continual worry. Jesse, could you describe your approach a little
> more? I assume you link the kernel with "ld -r" and have an elilo
> that applies the relocations?
I'm not sure that the mapping the kernel is quite as scary as it
appears to be:
1) All of the places where we need to take special care are in
initialization code.
2) Code that can be loaded as a module (which is a whole lot of
code) cannot make any assumptions about __pa() working on
addresses in .text/.data/.bss
A relocating elilo sounds interesting too (it passes the "don't
do things in the kernel unless you really have to" test).
-Tony
next prev parent reply other threads:[~2002-10-23 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 3:21 [Linux-ia64] ia64 compressed makefile target Jesse Barnes
2002-10-23 9:26 ` Andreas Schwab
2002-10-23 15:47 ` Jesse Barnes
2002-10-23 17:46 ` Luck, Tony
2002-10-23 19:01 ` David Mosberger
2002-10-23 20:43 ` Luck, Tony [this message]
2002-10-23 20:49 ` Jesse Barnes
2002-10-23 20:59 ` Jack Steiner
2002-10-23 21:08 ` David Mosberger
2002-10-23 21:20 ` Jesse Barnes
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=marc-linux-ia64-105590709805217@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.