lkml.org 
[lkml]   [2002]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] linux-2.5.43_vsyscall_A0
Date
From
johnstul@us.ibm.com said:
> Since no one really brought up any issues with the code itself
> (correct me if I'm wrong), here is the i386 vsyscall gettimeofday port
> I sent last night, synced up and ready for integration.

This vsyscall implementation breaks UML. Any app that's run inside UML
that uses vsyscalls will get the host's vsyscalls rather than the UML
vsyscalls.

This needs to be virtualizable somehow, which means that apps run inside
UML, without being changed, get the UML vsyscalls. There are a couple of
possiblities that I can think of:
a get_vsyscall system call which is executed by libc on startup -
UML would return a different calue from the host
some mechanism for UML to map its own vsyscall area in place of
the host's - it wouldn't necessarily need to be able to unmap it when it's
running its own kernel code because it can probably arrange not to use the
host's vsyscalls.

Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:30    [W:0.221 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site