All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Werner Almesberger <wa@almesberger.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dynamic syscalls revisited
Date: Tue, 14 Dec 2004 22:35:26 -0500	[thread overview]
Message-ID: <1103081726.3582.72.camel@localhost.localdomain> (raw)
In-Reply-To: <1103076859.3582.66.camel@localhost.localdomain>

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


      reply	other threads:[~2004-12-15  3:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 15:11 [PATCH][RFC] dynamic syscalls revisited Steven Rostedt
2004-11-29 15:17 ` Christoph Hellwig
2004-11-29 15:36   ` Steven Rostedt
2004-11-30 19:30     ` Kristian Sørensen
2004-11-29 16:41   ` [RFC] " Jan Engelhardt
2004-11-29 17:10     ` Steven Rostedt
2004-12-05 23:46       ` Adrian Bunk
2004-12-06 16:07         ` Steven Rostedt
2004-12-06 17:16           ` Steven Rostedt
2004-12-06 17:32             ` Zwane Mwaikambo
2004-12-06 17:57               ` linux-os
2004-12-06 18:03               ` Steven Rostedt
2004-12-06 18:18               ` Arjan van de Ven
2004-12-07  0:20           ` Michael Buesch
2004-12-07  0:57             ` Steven Rostedt
2004-12-06 21:14     ` H. Peter Anvin
2004-12-06 22:01       ` Steven Rostedt
2004-12-06 22:20         ` H. Peter Anvin
2004-12-06 22:38           ` Steven Rostedt
2004-12-14 23:14             ` Werner Almesberger
2004-12-15  2:14               ` Steven Rostedt
2004-12-15  3:35                 ` Steven Rostedt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1103081726.3582.72.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa@almesberger.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.