Messages in this thread | | | Subject | Re: [RFC] dynamic syscalls revisited | From | Steven Rostedt <> | Date | Tue, 14 Dec 2004 22:35:26 -0500 |
| |
On Tue, 2004-12-14 at 21:14 -0500, Steven Rostedt wrote: > On Tue, 2004-12-14 at 20:14 -0300, Werner Almesberger wrote: > > Steven Rostedt wrote: > > > It can be easier to send the wrong command to a device, or even the > > > wrong device than to use a wrong system call. > > > > So invent some /dev/syscall/<syscall-device-name> and you've reduced > > this to good old clashes in a flat name space. You can hide all the > > ugliness, sanity checking, etc. in a library. > > > > Already working on something. But I was a little distracted by some real > work :-) But I'll have a little device driver that can implement > dynamic system calls soon, and a library that will hide the real > ugliness. > > > I also think that a more direct approach for dynamic syscalls would > > be nice, but the current status quo is far from unbearable. > > > >
OK, my first attempt at a hack is done. If anyone wants a quick and nasty dynamic system call interface, here it is. It should work on any arch, although it is not user space thread safe (SMP safe though). It dynamically creates a device that implements system calls through it. It's a hack, but it gets around the kernel maintainers from forbidding dynamic system calls.
get it here: http://home.stny.rr.com/rostedt/dynamic/dsyscall_dev.tgz
-- Steve
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |