From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Feb 2003 17:02:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Feb 2003 17:02:11 -0500 Received: from [195.223.140.107] ([195.223.140.107]:18050 "EHLO athlon.random") by vger.kernel.org with ESMTP id ; Thu, 20 Feb 2003 17:02:09 -0500 Date: Thu, 20 Feb 2003 23:10:27 +0100 From: Andrea Arcangeli To: Jeff Garzik Cc: Prasad , lkml Subject: Re: Syscall from Kernel Space Message-ID: <20030220221027.GA31480@x30.school.suse.de> References: <20030220174043.GI9800@gtf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030220174043.GI9800@gtf.org> User-Agent: Mutt/1.4i X-GPG-Key: 1024D/68B9CB43 X-PGP-Key: 1024R/CB4660B9 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 20, 2003 at 12:40:43PM -0500, Jeff Garzik wrote: > On Thu, Feb 20, 2003 at 11:04:37PM +0530, Prasad wrote: > > Is there a way using which i could invoke a syscall in the kernel > > space? The syscall is to be run disguised as another process. The actual > > Call sys_. Look at the kernel code for examples. > > Note that typically you don't want to do this... and you _really_ don't > want to do this if the syscall is not one of the common file I/O > syscalls (read/write/open/close, etc.) you never want to do this, the only point of a syscall is to enter kernel, if you're just in kernel you're wasting time in calling the syscall (not to tell about the new non soft interrupt based syscall instructions, btw this is also why I rejected the int 0x81 thing on x86-64 for 64bit syscalls) Andrea