All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] user emulation status?
Date: Mon, 8 Sep 2008 17:31:00 +0300	[thread overview]
Message-ID: <20080908143100.GA923@kos.to> (raw)
In-Reply-To: <48C43986.3030903@wpkg.org>

On Sun, Sep 07, 2008 at 10:28:54PM +0200, Tomasz Chmielewski wrote:
> Debian Etch supports ARM, SPARC, PPC and MIPS, so I only tested those on 
> x86 PC.

Notice that etch doesn't use many of new syscalls introduced recently,
and doesn't use TLS/NPTL on many archs. So it's not really a very hard
test for qemu-user.

> Are you people interested in running processes in a foreign chroot (i.e. 
> ARM chroot on x86 PC)?

Yes. And I need to get my lazy ass off and start cleaning maemo/debian
linux-user patches and propose them here.

> I wanted to set up some daily automated tests which would fetch current 
> SVN, build for ARM, MIPS, PPC and SPARC targets, try to install Debian 
> with debootstrap in a chroot.

Since what we are actually emulating, is linux kernel syscall interface,
the most exhaustive test would be LTP. but debootstrapping debian is
good smoketest. Other nice tests could be perl/python/glibc testsuites.

-- 
"rm -rf" only sounds scary if you don't have backups

  parent reply	other threads:[~2008-09-08 14:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-07 20:28 [Qemu-devel] user emulation status? Tomasz Chmielewski
2008-09-08  6:16 ` Kirill A. Shutemov
2008-09-08 11:09 ` Thiemo Seufer
2008-09-08 14:31 ` Riku Voipio [this message]
2008-09-08 14:49   ` Tomasz Chmielewski
2008-09-08 15:04   ` Stuart Anderson
     [not found]   ` <48C64643.7050808@5etech.eu>
2008-09-09 17:07     ` Martin Mohring
2008-09-09 18:34 ` Miklos Vajna
2008-09-09 19:41   ` Martin Mohring
2008-09-09 20:01     ` Paul Brook
2008-09-09 21:16       ` michael
2008-09-09 21:19       ` Martin Mohring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080908143100.GA923@kos.to \
    --to=riku.voipio@iki.fi \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.