lkml.org 
[lkml]   [2002]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Voyager subarchitecture for 2.5.46

On Sun, 10 Nov 2002, Pavel Machek wrote:
>
> I believe you need to *store* last value given to userland.

But that's trivially done: it doesn't even have to be thread-specific, so
it can be just a global entry anywhere in the process data structures.

This is just a random sanity check thing, after all. It doesn't have to be
system-global or even per-cpu. The only really important thing is that
"gettimeofday()" should return monotonically increasing data - and if it
doesn't, the vsyscall would have to ask why (sometimes it's fine, if
somebody did a settimeofday, but usually it's a sign of trouble).

But yes, it's certainly a lot more complex than just doing it in a
controlled system call environment. Which is why I think vsyscalls are
eventually not worth it.

Linus

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