From owner-freebsd-threads@FreeBSD.ORG Wed Nov 26 22:22:32 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ADDD16A4CE for ; Wed, 26 Nov 2003 22:22:32 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32E6A43F3F for ; Wed, 26 Nov 2003 22:22:31 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id hAR6MU1G021716; Thu, 27 Nov 2003 01:22:30 -0500 (EST) Date: Thu, 27 Nov 2003 01:22:30 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Marcel Moolenaar In-Reply-To: <20031127055545.GB12712@dhcp01.pn.xcllnt.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: KSE/ia64 & thr_spinlock.c:1.18: problem identified X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 06:22:32 -0000 On Wed, 26 Nov 2003, Marcel Moolenaar wrote: > Ok, > > I found what the problem is. Syscalls that got interrupted were not > restarted when they should be. This is the result of using the KSE > internal context functions, when we should be going through the > kernel. So, the end result is that we do in fact need a syscall to > switch KSE contexts. Attached a patch to add such syscall. Please > review (ia64 specific changes to make use of the syscall are not > included). We don't need this for x86 or amd64, at least AFAICT, correct? How does a context get marked so one knows that you need to use kse_switchin()? BTW, why do we have to go through the kernel for ia64 in this case? -- Dan Eischen