From owner-cvs-all  Sun Apr 21  1: 9:41 2002
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 D27C837B416; Sun, 21 Apr 2002 01:09:37 -0700 (PDT)
Received: (from bde@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g3L89bT82731;
	Sun, 21 Apr 2002 01:09:37 -0700 (PDT)
	(envelope-from bde)
Message-Id: <200204210809.g3L89bT82731@freefall.freebsd.org>
From: Bruce Evans <bde@FreeBSD.org>
Date: Sun, 21 Apr 2002 01:09:37 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/kern kern_subr.c
X-FreeBSD-CVS-Branch: RELENG_4
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@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

bde         2002/04/21 01:09:37 PDT

  Modified files:        (Branch: RELENG_4)
    sys/kern             kern_subr.c 
  Log:
  MFC (part of 1.34: set p->p_priority in uio_yield() _after_ entering
  the "criticial region".  This merge is mainly for completeness.  Wrong
  settings of p->p_priority just modify the indeterminacy of scheduling,
  and this setting is not as wrong as some others -- I believe it is
  harmless in the current implementation of the scheduler.  The bug just
  turned up in a search for settings of p_priority that don't maintain
  certain invariants.
  
  Revision  Changes    Path
  1.31.2.2  +2 -2      src/sys/kern/kern_subr.c

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