Subject: Re: OT: calling kernel syscall manually
From: David Woodhouse <dwmw2@infradead.org>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: guest01 <guest01@gmail.com>, linux-kernel@vger.kernel.org
In-Reply-To: <450717A5.90509@cfl.rr.com>
References: <4506A295.6010206@gmail.com>
	 <1158068045.9189.93.camel@hades.cambridge.redhat.com>
	 <450717A5.90509@cfl.rr.com>
Content-Type: text/plain
Date: Tue, 12 Sep 2006 23:43:39 +0100
Message-Id: <1158101019.18619.113.camel@pmac.infradead.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 875
Lines: 21

On Tue, 2006-09-12 at 16:25 -0400, Phillip Susi wrote:
> 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.

No. If you do the inline assembly (or call the vDSO) yourself of course
it's still possible.

However, the _example_ that the OP gave of this 'third one' was in fact
using the old _syscallX() macros which used to be found in the kernel's
private header files. So I assumed that's what he meant, rather than
open-coding his own inline assembly.

-- 
dwmw2

-
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/