From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <ak@suse.de>
Cc: Suleiman Souhlal <ssouhlal@freebsd.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
vojtech@suse.cz, Jiri Bohac <jbohac@suse.cz>
Subject: Re: [PATCH 0/2] Make the TSC safe to be used by gettimeofday().
Date: Tue, 14 Nov 2006 08:42:33 +0100 [thread overview]
Message-ID: <1163490154.15249.235.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200611140250.57160.ak@suse.de>
On Tue, 2006-11-14 at 02:50 +0100, Andi Kleen wrote:
> On Tuesday 14 November 2006 02:06, Suleiman Souhlal wrote:
> > I've had a proof-of-concept for this since August, and finally got around to
> > somewhat cleaning it up.
>
> Thanks.
>
> I got a competing implementation for this unfortunately now from Vojtech & Jiri
where is this posted?
Since last weeks discussion on tickless several people started
implementing alternatives since nothing existed in public ...
prev parent reply other threads:[~2006-11-14 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 1:06 Suleiman Souhlal
2006-11-14 1:08 ` [PATCH 1/2] " Suleiman Souhlal
2006-11-14 2:05 ` Andi Kleen
2006-11-14 2:25 ` Suleiman Souhlal
2006-11-14 2:44 ` Andi Kleen
2006-11-14 3:35 ` dean gaudet
2006-11-14 4:22 ` dean gaudet
2006-11-14 3:54 ` Suleiman Souhlal
2006-11-14 11:12 ` Andi Kleen
2006-11-14 1:09 ` [PATCH 2/2] Introduce a vmonotonic_clock() vsyscall Suleiman Souhlal
2006-11-14 1:50 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() Andi Kleen
2006-11-14 2:06 ` Suleiman Souhlal
2006-11-14 11:10 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() II Andi Kleen
2006-11-14 12:30 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() Shem Multinymous
2006-11-14 17:06 ` Suleiman Souhlal
2006-11-14 18:30 ` Andi Kleen
2006-11-14 21:28 ` Christoph Lameter
2006-11-14 7:42 ` Arjan van de Ven [this message]
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=1163490154.15249.235.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ak@suse.de \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ssouhlal@freebsd.org \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®