From owner-p4-projects@FreeBSD.ORG Mon Nov 15 21:36:34 2004 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 3D2D116A4D1; Mon, 15 Nov 2004 21:36:34 +0000 (GMT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A2D116A4CE for ; Mon, 15 Nov 2004 21:36:34 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAC5C43D2F for ; Mon, 15 Nov 2004 21:36:33 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAFLZ3qe030234; Mon, 15 Nov 2004 16:35:03 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iAFLZ3Si030231; Mon, 15 Nov 2004 16:35:03 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Mon, 15 Nov 2004 16:35:03 -0500 (EST) From: "Andrew R. Reiter" To: Wayne Salamon In-Reply-To: <6BB8D529-374D-11D9-B0DF-00306540DC16@computer.org> Message-ID: <20041115163220.F29225@fledge.watson.org> References: <200411152057.iAFKvLYu013067@repoman.freebsd.org> <6BB8D529-374D-11D9-B0DF-00306540DC16@computer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Perforce Change Reviews Subject: Re: PERFORCE change 65203 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 21:36:34 -0000 On Mon, 15 Nov 2004, Wayne Salamon wrote: : :On Nov 15, 2004, at 3:58 PM, Andrew R. Reiter wrote: : :> Curious since I'll probably hack on this a bit later today: :> :> Are you dealing with the freebsd32 syscall masters as well? :> : : I was going to do that next. : Cool. :> I am going to also investigate if pecoff support is actually used or is :> rotting to hell... so may want to stay away from that piece if theres :> anything that requires modification there. :> : : OK. : : After freebsd32 changes are made, I need to figure out how to test :this. Couple ideas come to mind (not sure how good / bad they are): 1) we write a module that can be loaded and calls the syscalls from within the kernel with data formated properly. 2) we write a module that can force the setting of which syscall vector to be used... ie, setup a sysctl value that can be toggled to the various vectors and then have a set of *.c files to setup data properly and test? hmm.. perhaps PEter wemm has a good thought or two -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org