RE: Kernel Interface Page Dumping Server

[Volkmar Uhlig]

> -----Original Message-----
> From: Espen Skoglund 
> Sent: Wednesday, May 07, 2003 2:42 PM
> 
> > [Marcus Brinkmann]
> > Hmm, this is interesting.  I was thinking about having it in the
> > glibc startup function.  Having them set up in ld.so directly is
> > even better.  It sounds just a tiny bit hackish though.  If you
> > define the KIP address system wide for all tasks, you could also
> > avoid the need for such a fixup and compile the addresses statically
> > into the program.
> 
> Compiling it statically into the program is inflexible.  If the KIP is
> located at a high address it effectively prevents small spaces from
> ever being used.  If it is located at a low address it might have
> other consequences that we can not yet foresee.  The only way to allow
> for complete future flexibility is to allocate the KIP dynamically.

Not just that but also incorrect, since the KIP contains _pointers_ to
syscall stubs. Therefore, you have to link against the content (which is
dynamic and relative to the KIP address), not the KIP locations. 

Furthermore, you may not want to access the KIP for each syscall
basically pinning one additional data TLB entry per address space.

- Volkmar