From owner-freebsd-current  Thu Jun 11 02:50:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA01659
          for freebsd-current-outgoing; Thu, 11 Jun 1998 02:50:38 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01545;
          Thu, 11 Jun 1998 02:50:14 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA32032;
	Thu, 11 Jun 1998 19:42:42 +1000
Date: Thu, 11 Jun 1998 19:42:42 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806110942.TAA32032@godzilla.zeta.org.au>
To: bde@zeta.org.au, tlambert@primenet.com
Subject: Re: Spurious SIGXCPU
Cc: current@FreeBSD.ORG, jdp@polstra.com, phk@FreeBSD.ORG, rb@gid.co.uk
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Apparently your process appeared to run for a negative amount of time.
>> p_runtime is unsigned (64 bits), so negative runtimes are interpreted
>> as huge runtimes, even huger than RLIMIT_INFINITY.  This bug used to
>> be avoided by using signed variables even to hold values that should
>> be non-negative.
>
>Shouldn't accounting be done using monotime?

It already uses microuptime().  The monotime variable went away 2 months
ago.

>Ie: shouldn't accounting only be subject to positive drift?

It should, but there may be bugs.  I fixed 2 bugs, but they only caused
positive drift :-).  The main one was that the time to exit was often
counted twice.

Bruce

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