delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/02/11/17:31:22

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
Date: Fri, 11 Feb 2005 17:31:19 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: hyperthreading fix try #2
Message-ID: <20050211223119.GA29168@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
User-Agent: Mutt/1.4.1i

The latest snapshot has my latest try at fixing the dreaded
hyperthreading problem.  My previous fix was flawed in that once Corinna
corrected a typo in my change, the problem showed up again.

So, I've reworked the synchronization logic again and even ran cygwin
through that "test suite" thing that is all the rage with cygwin
developers these days.  In fact, I ran the test suite while running the
hyperthreading tests.

To test this, I ran two invocations of the standard shell script test
along with the Brian Ford variation of the same for 24 hours.  For some
reason, Brian's shell script seemed to trip the error more quickly than
the other one but the combination of running his script + the other
script seemed to produce the problem even more quickly.

(I'd modified both of the scripts so that they beeped if they exited,
causing me to jump out of my chair a couple of times as I struggled to
get this right.)

I'm not claiming that it is right now.  I haven't tried a "make -j" test
yet.  I just thought it was time to release another try on the world
again:

http://cygwin.com/snapshots/

To help preserve my tenuous grasp on sanity, please reply to *this
thread* when reporting problems.  Please don't start a new thread.  Just
reply here so that mailing list threading is preserved and I can easily
check for all success or error reports.  As before, any kind of report
is welcome but it is unlikely that I'm going to spend a lot of time
debugging problems that I can't reproduce.

cgf

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019