Re: [Fwd: RE: elf header bits for page migration support......]

From: H. J. Lu <>
Date: 2005-05-16 14:42:07
On Sun, May 15, 2005 at 11:29:55PM -0500, Ray Bryant wrote:
> H. J. Lu wrote:
> >
> >I didn't follow the whole thread very closely. But I can say
> >
> >1. We should use a dummy segement instead of bits in ELF header.
> >2. has no problems with more than one PT_LOAD segment. Most
> >of binaries/DSOs have 2: one is readonly and executable, the other
> >is read and write.
> >
> >If you want to modify to support your scheme, you can mark it
> >any PT_XXX you want. If you don't need/want to modify, you can
> >use a new PT_XXX and deal it in the user code. will ignore the
> >unknow PT_XXX. The static linker can provide _start/_end symbols for
> >the new PT_XXX segment.
> >
> >
> >H.J.
> >
> If we use a new segment at the end of the file (Jack had suggested this),
> then don't we have to scan the entire file before we find out that the 
> executable has this special section?  That makes it hard, because we call
> mmap() in and execve() [inside the kernel] as each segment is
> encountered.  So we need to know before that mmap() call is made whether
> or not the migration attribute needs to be added to that mmap'd region.

All necessary information of any segment should be in the ELF program
header. Looking it up is very straight forward in kernel and

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Mon May 16 00:42:28 2005

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:39 EST