Date: Fri, 07 Jun 2002 10:54:17 -0600 (MDT) From: "M. Warner Losh" <imp@village.org> To: jhb@FreeBSD.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, dwmalone@maths.tcd.ie Subject: Re: cvs commit: src/sys/kern kern_sig.c Message-ID: <20020607.105417.122245999.imp@village.org> In-Reply-To: <XFMail.20020607123811.jhb@FreeBSD.org> References: <20020607.095516.116907129.imp@village.org> <XFMail.20020607123811.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <XFMail.20020607123811.jhb@FreeBSD.org>
John Baldwin <jhb@FreeBSD.org> writes:
:
: On 07-Jun-2002 M. Warner Losh wrote:
: > In message: <XFMail.20020607091038.jhb@FreeBSD.org>
: > John Baldwin <jhb@FreeBSD.org> writes:
: >: You mean the SIGXCPU that is commented out in mi_switch()? It will
: >: be turned back on when I or someone else figures out how to do it
: >: safely. :)
: >
: > I thought that was commented out due to a bug where time would go
: > backwards every so often, causing there to be 2^32 or so time to be
: > charged to the process, which put it over the limit.
:
: It's commented out because of locking problems. mi_switch() is often
: called with p_stat set to something else like SSLEEP or what not. If
: we block on the proc lock to do the psignal, then when we finally get
: the lock p_stat will be SRUN. We might be able to do the check at the
: very end of mi_switch() though.
OK. I was getting confused between this bug and an older, timecounter
bug from 2.2.x
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020607.105417.122245999.imp>