From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgOUg-0006iV-1a for qemu-devel@nongnu.org; Thu, 29 Dec 2011 17:30:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RgOUe-0005QI-Hx for qemu-devel@nongnu.org; Thu, 29 Dec 2011 17:30:38 -0500 Received: from mail-yx0-f173.google.com ([209.85.213.173]:58717) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RgOUe-0005QD-E6 for qemu-devel@nongnu.org; Thu, 29 Dec 2011 17:30:36 -0500 Received: by yenm6 with SMTP id m6so9075836yen.4 for ; Thu, 29 Dec 2011 14:30:35 -0800 (PST) Message-ID: <4EFCEA07.4010000@codemonkey.ws> Date: Thu, 29 Dec 2011 16:30:31 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <4EEF70B4.3070109@us.ibm.com> <4EF73EF5.8050606@redhat.com> <4EF88EC0.8020301@codemonkey.ws> <4EF8FC88.70809@redhat.com> <4EFA4829.4000207@redhat.com> <4EFA80EA.3050405@codemonkey.ws> <4EFAA2A2.4000107@redhat.com> <4EFB2764.7040006@codemonkey.ws> <4EFB2F36.2090408@redhat.com> <4EFB35AB.6040003@redhat.com> <4EFB4757.4020504@codemonkey.ws> <4EFB5138.5020502@redhat.com> <4EFC916E.4070902@codemonkey.ws> <4EFC9706.4090500@redhat.com> <4EFCA2AF.5000806@redhat.com> <4EFCB30E.9030002@codemonkey.ws> <4EFCDFD2.3060307@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [ANNOUNCE] qemu-test: a set of tests scripts for QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "lmr@redhat.com" , Stefan Hajnoczi , cleber@redhat.com, dlaor@redhat.com, qemu-devel , Avi Kivity , Cleber Rosa , Gerd Hoffmann On 12/29/2011 04:10 PM, Peter Maydell wrote: > On 29 December 2011 21:46, Anthony Liguori wrote: >> But 0% test coverage is absolutely not enough. So the first step is to get >> an infrastructure together that we can all live with and start writing >> tests. > > Agreed. > > How does your framework deal with non-x86 targets? http://git.qemu.org/qemu-jeos.git I've already got ppc32 support working. Adding a new arch is just a matter of adding a kernel config and uClibc config to configs/ > Finding and > installing a working crosscompiler can be painful, especially if > you wanted to crosscompile userspace rather than just the kernel... I spent a couple days researching what to do here and ended up settling on: 1) build binutils for desired target 2) build GCC using (1) as a cross compiler. This is a limited form of GCC (no thread support) targeted as uClibc 3) build kernel using (2) and installer headers into our new sysroot 4) build uClibc using (2) and (3) 5) build busybox using (2) and (4) The whole process takes about 30 minutes on my laptop using -j1 which isn't all that bad. It's certainly faster than doing a distro install with TCG :-) qemu-jeos.git contains git submodules for binutils, GCC, linux, uClibc, and busybox plus miscellaneous scripts needed to make a working initramfs. Once we get more ARCHs working, I'll add a cronjob to qemu.org to build weekly binary packages so that for most people, all you have to do is grab an RPM/DEB with prebuilt binaries. Regards, Anthony Liguori > > -- PMM >