From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Machek <pavel@suse.cz>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"J.E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Voyager subarchitecture for 2.5.46
Date: Sun, 10 Nov 2002 20:48:11 +0100 [thread overview]
Message-ID: <20021110204811.B15515@ucw.cz> (raw)
In-Reply-To: <20021110194204.GF3068@atrey.karlin.mff.cuni.cz>; from pavel@suse.cz on Sun, Nov 10, 2002 at 08:42:04PM +0100
On Sun, Nov 10, 2002 at 08:42:04PM +0100, Pavel Machek wrote:
> Hi!
>
> > > 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).
>
> I believe you need it system-global. If task A tells task B "its
> 10:30:00" and than task B does gettimeofday and gets "10:29:59", it
> will be confused for sure.
You just need to make sure the time difference is less than the speed of
light in the system times the distance between the two tasks. ;) Really,
relativity, and the limited speed of travel of information kicks in and
saves us here.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-11-10 19:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 20:45 Voyager subarchitecture for 2.5.46 J.E.J. Bottomley
2002-11-06 2:31 ` john stultz
2002-11-06 13:43 ` Alan Cox
2002-11-06 21:35 ` john stultz
2002-11-06 15:03 ` J.E.J. Bottomley
2002-11-06 15:38 ` Alan Cox
2002-11-06 16:09 ` Christer Weinigel
2002-11-06 15:45 ` Linus Torvalds
2002-11-06 16:19 ` Alan Cox
2002-11-06 16:12 ` Linus Torvalds
2002-11-06 16:45 ` Alan Cox
2002-11-10 16:30 ` Pavel Machek
2002-11-10 18:59 ` Linus Torvalds
2002-11-10 19:18 ` Pavel Machek
2002-11-10 19:31 ` Linus Torvalds
2002-11-10 19:42 ` Pavel Machek
2002-11-10 19:48 ` Vojtech Pavlik [this message]
2002-11-10 20:02 ` Sean Neakums
2002-11-10 20:16 ` Lars Marowsky-Bree
2002-11-10 22:11 ` Alan Cox
2002-11-10 19:46 ` Vojtech Pavlik
2002-11-11 20:40 ` john stultz
2002-11-11 20:57 ` J.E.J. Bottomley
2002-11-11 21:36 ` William Lee Irwin III
2002-11-11 21:58 ` john stultz
2002-11-11 22:49 ` J.E.J. Bottomley
2002-11-11 23:12 ` john stultz
2002-11-12 12:16 ` Pavel Machek
2002-11-11 22:08 ` Vojtech Pavlik
2002-11-06 20:07 ` john stultz
2002-11-06 22:36 ` H. Peter Anvin
2002-11-06 19:30 ` john stultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021110204811.B15515@ucw.cz \
--to=vojtech@suse.cz \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox