Subject: Re: linker oddity on sparc
To: None <firstname.lastname@example.org, email@example.com>
From: None <firstname.lastname@example.org>
Date: 01/27/2001 23:29:09
Ok, I see.
It is currently a problem only for the kernel image in that the it's loaded
into memory causes that 64KB range of memory going completely to waste.
I'd say you have four options:
Use the linker's -N flag to join the data segment to the
text segment and make it a single writeable segment. This
means your text will be writeable (or, if you get clever with
the MMU, at least the last page may be writeable since it may
also contain data).
Have the loader load both segments contiguously and use MMU
magic to relocate them to the right addresses.
Write a custom linker script that separates the two segments
at the machine page boundary.
Do what you're currently doing, then add the 64KB section to
the VM system to manage.