From: Michael Buesch <mbuesch@freenet.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
LKML <linux-kernel@vger.kernel.org>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [RFC] dynamic syscalls revisited
Date: Tue, 7 Dec 2004 01:20:00 +0100 [thread overview]
Message-ID: <200412070120.05996.mbuesch@freenet.de> (raw)
In-Reply-To: <1102349255.25841.189.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
Quoting Steven Rostedt <rostedt@goodmis.org>:
> Done!
>
> Updated on http://home.stny.rr.com/rostedt/dynamic as well as included
> in this email for ease.
>
> Now, I guess you can still get around this if the "Bad Vendor" were to
> write a GPL module with their added system calls, and have that module
> include hooks to their binary module. So, until we can fix that, I
> guess Linus won't allow for this module to be included in the main line.
>
> -- Steve
[SNIP]
> Index: arch/i386/kernel/entry.S
> ===================================================================
> --- arch/i386/kernel/entry.S (revision 15)
> +++ arch/i386/kernel/entry.S (working copy)
> @@ -906,5 +906,10 @@
> .long sys_vperfctr_unlink
> .long sys_vperfctr_iresume
> .long sys_vperfctr_read
> +#ifdef CONFIG_DSYSCALL
> + .long sys_dsyscall /* 295 */
> +#else
> + .long sys_ni_syscall /* 295 */
> +#endif
Wouldn't it be better to do a
cond_syscall(sys_dsyscall)
in kernel/sys_ni.c
--
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-07 0:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 15:11 [PATCH][RFC] " 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 [this message]
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
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=200412070120.05996.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome