lkml.org 
[lkml]   [2002]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] linux-2.5.43_vsyscall_A0
On Sat, Oct 19, 2002 at 05:52:53AM +0200, Jeff Dike wrote:
> 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.

Ugh.

Guess you'll have some problems then with UML on x86-64, which always uses
vgettimeofday. But it's only used for gettimeofday() currently, perhaps it's
not that bad when the UML child runs with the host's time.

I guess it would be possible to add some support for UML
to map own code over the vsyscall reserved locations. UML would need
to use the syscalls then. But it'll be likely ugly.

-Andi
-
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.094 / U:0.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site