From: Phillip Susi <psusi@cfl.rr.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: guest01 <guest01@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: OT: calling kernel syscall manually
Date: Tue, 12 Sep 2006 16:25:09 -0400 [thread overview]
Message-ID: <450717A5.90509@cfl.rr.com> (raw)
In-Reply-To: <1158068045.9189.93.camel@hades.cambridge.redhat.com>
What do you mean you have removed the ability to make system calls
directly? That makes no sense. Glibc has to be able to make system
calls so you can write your own code that does the same thing if you want.
For the OP: you might want to study the glibc sources to see how it
implements syscall, and mimic that. IIRC it involves making an int 80
call on i386.
David Woodhouse wrote:
> The third one has always been broken on i386 for PIC code and was
> pointless anyway, since glibc provides this functionality. The kernel
> method has been removed from userspace visibility all architectures, and
> we plan to remove it entirely in 2.6.19 since it's not at all useful.
>
> However, there was a patch which was sneaked to Linus in private which
> reverted that cleanup on i386 and x86_64 and made them visible again --
> but they'll be going away again on those two architectures shortly;
> hopefully before 2.6.18.
>
> Don't bother with it -- just use glibc's syscall().
>
next prev parent reply other threads:[~2006-09-12 20:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 12:05 OT: calling kernel syscall manually guest01
2006-09-12 13:34 ` David Woodhouse
2006-09-12 14:31 ` guest01
2006-09-12 14:37 ` David Woodhouse
2006-09-12 20:25 ` Phillip Susi [this message]
2006-09-12 20:46 ` Miguel Ojeda
2006-09-12 22:03 ` Arnd Bergmann
2006-09-12 22:43 ` David Woodhouse
2006-09-13 16:52 ` guest01
2006-09-13 17:52 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2006-09-13 5:35 Albert Cahalan
2006-09-13 6:55 ` David Woodhouse
2006-09-13 15:52 ` Albert Cahalan
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=450717A5.90509@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dwmw2@infradead.org \
--cc=guest01@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.