From owner-cvs-all  Sun May 20 13: 4:43 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id C000E37B422; Sun, 20 May 2001 13:04:40 -0700 (PDT)
	(envelope-from bde@FreeBSD.org)
Received: (from bde@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f4KK4eL27905;
	Sun, 20 May 2001 13:04:40 -0700 (PDT)
	(envelope-from bde)
Message-Id: <200105202004.f4KK4eL27905@freefall.freebsd.org>
From: Bruce Evans <bde@FreeBSD.org>
Date: Sun, 20 May 2001 13:04:40 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/i386/isa npx.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

bde         2001/05/20 13:04:40 PDT

  Modified files:
    sys/i386/isa         npx.c 
  Log:
  Throw away the complications in npxsave() and their infrastructure.
  npxsave() went to great lengths to excecute fnsave with interrupts
  enabled in case executing it froze the CPU.  This case can't happen,
  at least for Intel CPU/NPX's.  Spurious IRQ13's don't imply spurious
  freezes.  Anyway, the complications were usually no-ops because IRQ13
  is not used on i486's and newer CPUs, and because SMPng broke them in
  rev.1.84.  Forcible enabling of interrupts was changed to
  write_eflags(old_eflags), but since SMPng usually calls npxsave() from
  cpu_switch() with interrupts disabled, write_eflags() usually just
  kept interrupts disabled.
  
  Revision  Changes    Path
  1.100     +24 -54    src/sys/i386/isa/npx.c


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message