Date: Tue, 5 Jun 2007 19:37:40 +0200 From: "Attilio Rao" <attilio@freebsd.org> To: "John Baldwin" <jhb@freebsd.org> Cc: Kostik Belousov <kostikbel@gmail.com>, cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: cvs commit: src/sys/kern kern_mutex.c Message-ID: <3bbf2fe10706051037n3442fc3cjc89501b42d1a5543@mail.gmail.com> In-Reply-To: <200706051327.21307.jhb@freebsd.org> References: <200706051420.l55EKEih018925@repoman.freebsd.org> <200706051230.21242.jhb@freebsd.org> <3bbf2fe10706051012x76381687g98e034ceb47b3f26@mail.gmail.com> <200706051327.21307.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2007/6/5, John Baldwin <jhb@freebsd.org>: > In the PREEMPTION case, the act of making the threads runnable will trigger a > preemption (or set td_owepreempt). The !PREEMPTION stuff is to make > mtx_unlock() preempt when PREEMPTION isn't enabled in the kernel. Yes, I just thought it wasn't due for the !PREEMPTION case. Attilio -- Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10706051037n3442fc3cjc89501b42d1a5543>