From owner-cvs-sys  Fri Sep  5 10:59:11 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA22389
          for cvs-sys-outgoing; Fri, 5 Sep 1997 10:59:11 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA22232;
          Fri, 5 Sep 1997 10:56:19 -0700 (PDT)
From: Peter Wemm <peter@FreeBSD.ORG>
Received: (from peter@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id KAA21045;
	Fri, 5 Sep 1997 10:54:09 -0700 (PDT)
Date: Fri, 5 Sep 1997 10:54:09 -0700 (PDT)
Message-Id: <199709051754.KAA21045@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/i386/i386 swtch.s
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

peter       1997/09/05 10:54:09 PDT

  Modified files:
    sys/i386/i386        swtch.s 
  Log:
  Argh, what was I thinking??  Don't (yet) halt the CPU in the idle loop
  while waiting for an interrupt (rather than spinning on the runqueue status
  bits), since the other cpu can put stuff in there and the sleeping cpu may
  not get an interrupt for a while.  When we have a reschedule IPI, this can
  come back.
  
  Pointed out by: fsmp
  
  Revision  Changes    Path
  1.61      +3 -1      src/sys/i386/i386/swtch.s