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
Date: Mon, 13 May 2002 09:56:58 +0100
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: <15591.64698.290124.380527@bea.com>
To: cygwin AT cygwin DOT com
Subject: Re: [PATCH] gettimeofday time travels
In-Reply-To: <15579.35225.764199.450263@bea.com>
References: <15547 DOT 16136 DOT 163472 DOT 840007 AT bea DOT com>
	<20020415214133.GA19612 at redhat.com>
	<15577.12319.622365.566799 at bea.com>
	<20020508144104.GA1093 at redhat.com>
	<15578.30482.568575.767214 at bea.com>
	<20020509160449.GF6910 at redhat.com>
	<15579 DOT 35225 DOT 764199 DOT 450263 AT bea DOT com>


Philip Aston writes:
 > Christopher Faylor writes:
 >  > 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.

Short of some unexpected wParam values, which I'll track down, I now
have this working.

I have some design questions. Please help me ensure my patch is up to
scratch..

1. Currently I'm leveraging the event loop for the hidden window that
is created for alarm and ualarm support (window.cc). This involves a
call to gethwnd() create that window if it doesn't exist. I presume
this is fine as the socket support does the same. Any objections?

2. Should I implement a generic mechanism for listening to power
events? Currently I've just added a static hires::reprime() method
which is called on the appropriate power event.

3. The reprime() method iterates over a linked list of hires objects.
The hires ctor inserts a hires into this list. Do I need to worry
about thread safety here? If so, what's a typical solution? I didn't
see any handy thread safe list.

4. Similarly for the dtor - I'm planning to assert here, rather than
faff with a double linked list. This means that hires's can never be
deleted. OK?


Thanks,

- 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/