Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond

[Rob Landley <rob@landley.net>]

On 08/13/2014 11:16 AM, Andy Lutomirski wrote:
> On Wed, Aug 13, 2014 at 9:11 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>> For my own qemu runtime tests, I ended up collecting root file systems and
>> kernel configurations from all over the place. And then there is the problem
>> of qemu command line parameters, where each target and architecture requires
>> its own set of options, and it is sometimes all but impossible to find a
>> working set of parameters for a given target/architecture combination.
>>
> 
> virtme has exactly this problem (except for the root image part --
> virtme can use debootstrap output directly).  In virtme, I'm trying to
> solve it by just collecting known-working QEMU arguments and
> documenting the corresponding kernel config requirements.

My aboriginal linux system is designed around the assumption that nobody
will ever actually bother to use it. (That's why I ship prebuilt binary
tarballs.)

I also write extensive documentation nobody will ever read:

http://landley.net/aboriginal/about.html

Each system-image tarball has a "run-emulator.sh" script that's just the
qemu invocation. If you want to know how to launch qemu for the target:
there you go.

The kernel config is using the "miniconfig" technique:

http://landley.net/aboriginal/FAQ.html#dev_miniconfig

You assemble the miniconfig from the target-independent parts:

http://landley.net/hg/aboriginal/file/tip/sources/baseconfig-linux

And then concatenate the target-specific bits from the relevant
sources/targets file. ala:

http://landley.net/hg/aboriginal/file/tip/sources/targets/i686#l19

(All the target-specific information is in a single file under
sources/targets. There are various patches in sources/patches some of
which are target specific. All of them should go upstream, but kernel
development is so insular it's just not worth the effort.)

If you don't want to use miniconfig, the expanded configs are in the
root-filesystem tarballs (in the src directory).

> --Andy
> .
>