Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755947AbYGGHBi (ORCPT ); Mon, 7 Jul 2008 03:01:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751457AbYGGHBa (ORCPT ); Mon, 7 Jul 2008 03:01:30 -0400 Received: from casper.infradead.org ([85.118.1.10]:33114 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750929AbYGGHB3 (ORCPT ); Mon, 7 Jul 2008 03:01:29 -0400 Date: Mon, 7 Jul 2008 00:01:28 -0700 From: Arjan van de Ven To: "Jinkai Gao" Cc: linux-kernel@vger.kernel.org Subject: Re: Suggestion: LKM should be able to add system call for itself Message-ID: <20080707000128.1e93d8e4@infradead.org> In-Reply-To: References: Organization: Intel X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 999 Lines: 27 On Mon, 7 Jul 2008 01:09:30 -0400 "Jinkai Gao" wrote: > Above is to demonstrate that LKM is extension to kernel, and the > system calls should be able to extend as long as the kernel is > extending. So The LKM should be able to define its own user interface > by adding new system call for itself. Since we promise a stable ABI to userspace, this is a bit of a problem. But... look today, we already have various system calls implemented by modules. (example: sys_nfsservctl) but to make it fully dynamic? Not a good idea... nobody would be able to program to it. -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/