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
ak@muc.de said:
> 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.

It's not horrible, but it's still broken. There are people who depend
on UML being able to keep its own time separately from the host.

> 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.

Yeah, it would be.

My preferred solution would be for libc to ask the kernel where the vsyscall
area is. That's reasonably clean and virtualizable. Andrea doesn't like it
because it adds a few instructions to the vsyscall address calculation.

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    [from the cache]
©2003-2011 Jasper Spaans