Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755538AbXIUEw0 (ORCPT ); Fri, 21 Sep 2007 00:52:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750752AbXIUEwT (ORCPT ); Fri, 21 Sep 2007 00:52:19 -0400 Received: from agminet01.oracle.com ([141.146.126.228]:58202 "EHLO agminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbXIUEwT (ORCPT ); Fri, 21 Sep 2007 00:52:19 -0400 Date: Thu, 20 Sep 2007 21:50:42 -0700 From: Randy Dunlap To: Sam Ravnborg Cc: Christoph Hellwig , David Wilder , Andi Kleen , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, Linus Torvalds Subject: Re: Test harness in the kernel for new syscalls? [Was: Trace code and documentation (updated)] Message-Id: <20070920215042.38fd3546.randy.dunlap@oracle.com> In-Reply-To: <20070919180115.GE3115@uranus.ravnborg.org> References: <1190177218.3190.18.camel@lc4eb748232119.ibm.com> <46F12ED7.3060605@us.ibm.com> <20070919162018.GA16237@infradead.org> <20070919095223.83bd8226.randy.dunlap@oracle.com> <20070919165507.GA18973@infradead.org> <20070919174845.GD3115@uranus.ravnborg.org> <20070919175109.GA23889@infradead.org> <20070919180115.GE3115@uranus.ravnborg.org> Organization: Oracle Linux Eng. X-Mailer: Sylpheed 2.4.6 (GTK+ 2.8.10; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2267 Lines: 56 On Wed, 19 Sep 2007 20:01:15 +0200 Sam Ravnborg wrote: > On Wed, Sep 19, 2007 at 06:51:09PM +0100, Christoph Hellwig wrote: > > On Wed, Sep 19, 2007 at 07:48:45PM +0200, Sam Ravnborg wrote: > > > > Well, this is kernel code - so util-linux is not the solution here > > > > obviously :) so kernel sample code goes in the new samples/ directory, and userspace sample code gets pushed to util-linux ? > > > Can you sketch what you have in mind. > > > We right now have said we wnated to: > > > 1) include a framework for executing simple new-syscall-test-stubs > > > 2) have a nice place for kernel example code > > > > > > I could come up with something but I expect you already have something > > > in your mind where to put stuff. > > > If I have a rough idea I can start looking into the kbuild bits of it. > > > Not that I will have it ready within the next two weeks but nice buffer > > > when I anyway drop sleeping.. > > > > I think for samples we just want a samples/ toplevel directory with > > normal Kbuild and Kconfig files. Not any different from drivers or > > filesystems, just a new hiearchary. > > OK - anyone can do this. So I will not worry. > > > > tests stuff was rather disliked by Linus, so I wonder wether we should > > go ahead with it. > I heard it like "Ok for new syscalls". > > And it is resonable for new syscalls because: > o Make the test of the syscall public > o Is a nice example of the usage of the syscalls (both good and bad cases) > o Is availbale for other platforms that plan to implement the same syscall > o We (at least a few sufficiently skilled ones) will then review not only > the syscall but also the use of the syscall That's a good idea/plan. > > We'd need a test driver like expect to driver the > > testcases. > OK - may give it a spin one day. > But I hope someone that have done similar stuff can come > with some example code we can adapt to the kernel. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - 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/