Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Philip Aston" <paston AT bea DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15579.35225.764199.450263@bea.com>
Date: Fri, 10 May 2002 09:49:29 +0100
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] gettimeofday time travels
In-Reply-To: <20020509160449.GF6910@redhat.com>
References: <15547 DOT 16136 DOT 163472 DOT 840007 AT bea DOT com>
	<20020415214133 DOT GA19612 AT redhat DOT com>
	<15577 DOT 12319 DOT 622365 DOT 566799 AT bea DOT com>
	<20020508144104 DOT GA1093 AT redhat DOT com>
	<15578 DOT 30482 DOT 568575 DOT 767214 AT bea DOT com>
	<20020509160449 DOT GF6910 AT redhat DOT com>


Christopher Faylor writes:
 > An NT only solution is not a solution.

I wasn't for a moment suggesting that it was.

 > Syncing every "x" seconds also is not a solution.
 > 
 > The correct solution is to resync after events which cause the clock to
 > stop.

OK, I'll have a crack at this over the weekend following David's
hints.

Looks straightforward. I'll patch the event loop in window.cc to set
some static flag in hires on suspend and/or resume events, and
reinitialise in hires::usecs iff the flag is set.

Let me know if I'm well off track here.

- Phil


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/