Re: elf loader is broken

• To: <oskit-users@fast.cs.utah.edu>
• Subject: Re: elf loader is broken
• From: Gopalakrishnan Suresh <gsuresh@research.bell-labs.com>
• Date: Mon, 8 Jul 2002 12:20:23 -0400 (EDT)
• In-Reply-To: <871yai2q8g.fsf@bassanio.walfield.org>
• Sender: owner-oskit-users@fast.cs.utah.edu

> The elf standard says that elf executables must be extracted to the
> physical load address, not the virtual memory address. This is not
> done in oskit/exec/elf.c--at least in the version released on March
> 17, 2002; I have attached a patch.

I am not so sure about this - isn't the p_paddr relevant only if direct
physical addressing is used (and there are no holes in physical memory)?
The loading and linking has to be architecture and OS specific?

IA32 provides the option of not using virtual memory (i.e. the page
tables), since protection can be achieved by using segmentation. Some
OSkit components happen to use page tables, but seem to perform a direct
mapping. So using p_vaddr or p_paddr might work the same way.

I think that if you use non-direct page table mapping (for protection or
for virtual memory i.e. swapping) then you would need to use p_vaddr.

--suresh

• elf loader is broken
• From: neal@cs.uml.edu (Neal H. Walfield)

• Prev: unsubscribe
• Next: Re: Address space question
• Index(es):
  • Main
  • Thread