From owner-freebsd-current Thu Jan 7 02:49:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05903 for freebsd-current-outgoing; Thu, 7 Jan 1999 02:49:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05898 for ; Thu, 7 Jan 1999 02:49:54 -0800 (PST) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.1/8.7.3) id LAA14240; Thu, 7 Jan 1999 11:50:54 +0100 (CET) To: current@FreeBSD.ORG Subject: Re: KLD modules support for loading syscalls References: <199901070547.VAA11410@kithrup.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 07 Jan 1999 11:50:53 +0100 In-Reply-To: Sean Eric Fagan's message of "Wed, 6 Jan 1999 21:47:50 -0800 (PST)" Message-ID: <5l67aj8igh.fsf@assaris.sics.se> Lines: 21 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan writes: > In article <5lsodneizm.fsf.kithrup.freebsd.current@assaris2.pdc.kth.se> you write: > >Questions, comments, bugs, and commits are welcome. > > Yeah. Did you give any thought how ktrace and truss are supposed to > work with this? :) No. But that doesn't have very much to do with how you add the system calls, only that they aren't in syscalls.master, right? Right now, it seems you get something like: syscall lkmnosys(0x14,0x0,0x800c5603,0xefbfd6cc,0x0) errno 22 'Invalid argument' which isn't that bad, even through the name and number would be better. Should we add a sysctl (or something else) interface for getting the syscall names? Moving the name into `struct sysent' seems to me like it would make sense anyway. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message