Date: Mon, 15 Nov 2004 16:35:03 -0500 (EST) From: "Andrew R. Reiter" <arr@watson.org> To: Wayne Salamon <wsalamon@computer.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 65203 for review Message-ID: <20041115163220.F29225@fledge.watson.org> In-Reply-To: <6BB8D529-374D-11D9-B0DF-00306540DC16@computer.org> References: <200411152057.iAFKvLYu013067@repoman.freebsd.org> <6BB8D529-374D-11D9-B0DF-00306540DC16@computer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041115163220.F29225>