Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Subject: Re: Hyperthreading Problem - suggestion
From: Adrian Cox <adrian AT humboldt DOT co DOT uk>
To: cygwin AT cygwin DOT com
In-Reply-To: <20050110172023.GA2023@trixie.casa.cgf.cx>
References: <GCEBKEBLOHKOGJEBHNNEAEBBGCAB DOT vbandke AT bsp-gmbh DOT com> <20050110172023 DOT GA2023 AT trixie DOT casa DOT cgf DOT cx>
Content-Type: text/plain
Date: Mon, 10 Jan 2005 20:49:20 +0000
Message-Id: <1105390160.1999.52.camel@newt>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On Mon, 2005-01-10 at 12:20 -0500, Christopher Faylor wrote:

> The last time I tried to duplicate the problem, I ran a test for three
> days, tying up a machine that I use for other purposes.  I'd previously
> tried other variations as well.  The system is an SMP system so there
> should have been a good chance of duplicating the bug.  I'm not going to
> try every variation of this problem when it shows up on the list.

Just a quick observation and a question. Hyperthreading exposed a race
condition in an NT driver of mine that had run for a long time on an SMP
system. The timing is different.

Is there anybody out there who has Windows XP and hyperthreading and
_can't_ reproduce the problem? This is making me nervous about a project
I'm planning, as most of the target machines will be P4s with
hyperthreading running XP. 

-- 
Adrian Cox <adrian AT humboldt DOT co DOT uk>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/