From owner-freebsd-threads@FreeBSD.ORG Thu Nov 27 07:07:28 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 0756E16A4CE for ; Thu, 27 Nov 2003 07:07:28 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01F8243FBF for ; Thu, 27 Nov 2003 07:07:27 -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 hARF7P1G017705; Thu, 27 Nov 2003 10:07:26 -0500 (EST) Date: Thu, 27 Nov 2003 10:07:25 -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 Reply-To: deischen@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Nov 2003 15:07:28 -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). The patch looks OK. Is it possible to roll _ia64_break_setcontext() into kse_switchin() and have ia64's set_mcontext() know the difference between the two contexts? -- Dan Eischen