From owner-cvs-src@FreeBSD.ORG Mon Jul 7 15:32:53 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6D7F37B401; Mon, 7 Jul 2003 15:32:53 -0700 (PDT) Received: from HAL9000.homeunix.com (ip114.bella-vista.sfo.interquest.net [66.199.86.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EA6343F85; Mon, 7 Jul 2003 15:32:53 -0700 (PDT) (envelope-from das@freebsd.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h67MWiK5094099; Mon, 7 Jul 2003 15:32:44 -0700 (PDT) (envelope-from das@freebsd.org) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h67MWfCq094098; Mon, 7 Jul 2003 15:32:41 -0700 (PDT) (envelope-from das@freebsd.org) Date: Mon, 7 Jul 2003 15:32:41 -0700 From: David Schultz To: Julian Elischer Message-ID: <20030707223241.GA94049@HAL9000.homeunix.com> Mail-Followup-To: Julian Elischer , David Xu , src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org References: <20030707082506.GA90638@HAL9000.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: David Xu cc: src-committers@freebsd.org cc: cvs-all@freebsd.org cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/lib/libpthread/thread thr_attr_get_np.c thr_cancel.c thr_getschedparam.c thr_join.c thr_mutex_prioceiling.c thr_sigaction.c thr_sigmask.c thr_sigpending.c thr_sigsuspend.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 22:32:54 -0000 On Mon, Jul 07, 2003, Julian Elischer wrote: > > That's what I was talking about. If you enter the UTS upon taking > > a page fault, you have to be sure that the page that faulted > > didn't belong to the UTS itself, or you at least have to have some > > way of breaking the loop. But since the UTS is unaware of page > > faults presently, I guess this isn't a problem yet. > > > > By definition, (i.e the definition of how upcalls are done) > a page fault in the UTS would block until the page was loaded and no > upcall would be produced.. This is because there is no registerred > 'thread' in the UTS's mailbox when the kernel is enterred, so > no upcall context can be created. (or, rather, the current context can > not be storred for later so the current KSE is not free to create a new > upcall context.) Thanks to both you and Dan, I am now un-confused. Moreover, it seems like someone (David?) fixed the sigwait() problems that have been plaguing me for a while now. KSE has really come a long way in the last few months!