From owner-cvs-all@FreeBSD.ORG Sun Jun 15 15:37:20 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B7F737B401; Sun, 15 Jun 2003 15:37:20 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0D6043FDF; Sun, 15 Jun 2003 15:37:18 -0700 (PDT) (envelope-from davidxu@freebsd.org) Received: from tiger (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with SMTP id h5FMbCUp020955; Sun, 15 Jun 2003 15:37:14 -0700 (PDT) (envelope-from davidxu@freebsd.org) Message-ID: <001101c3338f$1f4f81b0$0701a8c0@tiger> From: "David Xu" To: , , , "Julian Elischer" References: <20030615061909.4696637B401@hub.freebsd.org> Date: Mon, 16 Jun 2003 06:40:23 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: cvs commit: src/sys/alpha/alpha vm_machdep.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Xu List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jun 2003 22:37:21 -0000 ----- Original Message -----=20 From: "Julian Elischer" To: ; ; ; = Sent: Sunday, June 15, 2003 2:19 PM Subject: Re: cvs commit: src/sys/alpha/alpha vm_machdep.c > From: David Xu > davidxu 2003/06/14 17:54:07 PDT >=20 > FreeBSD src repository >=20 > Modified files: > sys/alpha/alpha vm_machdep.c=20 > Log: > Don't set TDF_UPCALLING in cpu_set_upcall, it is not only used by > SA process. > =20 > Revision Changes Path > 1.88 +0 -2 src/sys/alpha/alpha/vm_machdep.c > I think this is only part of the answer.. > If anyone else is using cpu-set_upcall then we should rename > it to "set_return_context" or something, since on SA has upcalls. >=20 >=20 A few of code is calling the function, 1:1 threading when creating a thread and SA process when scheduling an upcall. I think it is still manageable. David Xu