From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 21B638CC for ; Tue, 12 Aug 2014 17:31:00 +0000 (UTC) Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 42CCC20334 for ; Tue, 12 Aug 2014 17:30:59 +0000 (UTC) Received: by mail-la0-f46.google.com with SMTP id b8so8155753lan.19 for ; Tue, 12 Aug 2014 10:30:57 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <53EA3DA0.2070407@roeck-us.net> References: <53E38ED5.9000300@samsung.com> <53E43365.50809@hitachi.com> <53E8CF03.6020308@samsung.com> <53E8EB93.8030301@hitachi.com> <20140812130043.4894DC40C5C@trevor.secretlab.ca> <53EA3DA0.2070407@roeck-us.net> From: Andy Lutomirski Date: Tue, 12 Aug 2014 10:30:37 -0700 Message-ID: To: Guenter Roeck Content-Type: text/plain; charset=UTF-8 Cc: Greg KH , "ksummit-discuss@lists.linuxfoundation.org" , shuah.kh@samsung.com Subject: Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Aug 12, 2014 9:22 AM, "Guenter Roeck" wrote: > > On 08/12/2014 06:00 AM, Grant Likely wrote: >> >> On Tue, 12 Aug 2014 01:13:07 +0900, Masami Hiramatsu wrote: >>> >>> (2014/08/11 23:11), Shuah Khan wrote: >>>>> >>>>> (2014/08/07 23:36), Shuah Khan wrote:> As a first step towards a larger goal to enable developer >>>>>> >>>>>> friendly kernel testing framework, a new make target is >>>>>> planned for 3.17. In addition, 3.17 includes work done to >>>>>> fix tools/testing/sefltests to run without failures. >>>>>> >>>>>> Short summary of work done so far for 3.17: >>>>>> >>>>>> - fix compile errors and warnings in various tests >>>>>> - fix run-time errors when tests aren't run as root >>>>>> - enhance and improve cpu and memory hot-plug tests >>>>>> to run in limited scope mode by default. A new make >>>>>> target to select full-scope testing. Prior to this >>>>>> change, cpu and memory hot-plug tests hung trying to >>>>>> hot-plug all but cpu0 and a large portion of the memory. >>>>>> - add a new kselftest target to run existing selftests >>>>>> to start with. >>>>> >>>>> >>>>> Instead of running the selftests, can we build the testcases and >>>>> install it as a tool? I think running tests on the tree is not a >>>>> good idea... >>>> >>>> >>>> One of the goals is to leverage developer tests that we already have. >>>> When a developer makes a kernel change and wants to see if that change >>>> lead to any regression, having the ability to buidl and run selftests on >>>> the newly installed kernel withe the same source tree is very useful. >>>> That is the reason behind adding this new target. >>> >>> >>> I see, for that purpose, installing testcase may not fit. >>> BTW, how would it cover cross-build? >> >> >> I'm interested in this as well. I'm working on a tool that crossbuilds a >> very simple busybox rootfs and boots in QEMU for as many architectures >> as possible. I want to make it easy to sanity test all the major >> architectures. Right now it does little more than boot to a login >> prompt, but I'd like to get the kselftests into it also. >> > > Do you have that public yet ? I might want to use that for my -stable sanity tests. I've been working on a somewhat orthogonal approach: I have a script that boots a kernel from a bunch of files, including, optionally, the host system. So far, it supports x86 and arm, but adding architectures is very simple -- it just needs some hints for how to invoke QEMU. https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git One of virtme's explicit goals is to make it easy to boot a kernel, run a script, and shut down. The syntax for that is a bit awkward right now, but it works. It still needs a rootfs for non-native boots, so your tool could help with that. --Andy