From: "Shem Multinymous" <multinymous@gmail.com>
To: "Suleiman Souhlal" <ssouhlal@freebsd.org>
Cc: "Andi Kleen" <ak@suse.de>,
"Linux Kernel ML" <linux-kernel@vger.kernel.org>,
vojtech@suse.cz, "Jiri Bohac" <jbohac@suse.cz>,
"Nigel Cunningham" <ncunningham@cyclades.com>,
"Pavel Machek" <pavel@suse.cz>
Subject: Re: [PATCH 0/2] Make the TSC safe to be used by gettimeofday().
Date: Tue, 14 Nov 2006 14:30:38 +0200 [thread overview]
Message-ID: <41840b750611140430k3b46023dr9a01b8b38bbb535d@mail.gmail.com> (raw)
In-Reply-To: <45592497.1080109@FreeBSD.org>
On 11/14/06, Suleiman Souhlal <ssouhlal@freebsd.org> wrote:
> I believe that the results returned will always be monotonic, as long as
> the frequency of the TSC does not change from under us (that is, without
> the kernel knowing). This is because we "synchronize" each CPU's vxtime
> with a global time source (HPET) every time we know the TSC rate changes.
Does this hold after a suspend/resume cycle? You could be resuming
with a different CPU clock than what you suspended with, and I'm not
sure anything guarantees an early enough re-sync.
Shem
next prev parent reply other threads:[~2006-11-14 12:30 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 ` Shem Multinymous [this message]
2006-11-14 17:06 ` [PATCH 0/2] Make the TSC safe to be used by gettimeofday() 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
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=41840b750611140430k3b46023dr9a01b8b38bbb535d@mail.gmail.com \
--to=multinymous@gmail.com \
--cc=ak@suse.de \
--cc=jbohac@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--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®