From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MEluQ-0002z7-Uz
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 11:09:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MEluP-0002uf-AR
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 11:09:42 -0400
Received: from [199.232.76.173] (port=49905 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MEluP-0002uU-6A
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 11:09:41 -0400
Received: from naru.obs2.net ([84.20.150.76]:44647)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <nchip@kos.to>) id 1MEluO-0004tn-Nw
	for qemu-devel@nongnu.org; Thu, 11 Jun 2009 11:09:41 -0400
Date: Thu, 11 Jun 2009 18:09:37 +0300
From: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on
	configure
Message-ID: <20090611150937.GA18020@kos.to>
References: <1244582792-30589-1-git-send-email-ehabkost@redhat.com>
	<1244582792-30589-3-git-send-email-ehabkost@redhat.com>
	<87ocsxoye4.fsf@lechat.rtp-net.org>
	<20090610141255.GZ18045@blackpad> <20090610160742.GB12221@kos.to>
	<20090610162047.GA7776@poweredge.glommer>
	<874ouonj9i.fsf@lechat.rtp-net.org>
	<20090610165640.GC7776@poweredge.glommer>
	<20090610220540.GE23525@kos.to> <87vdn3mapj.fsf@lechat.rtp-net.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87vdn3mapj.fsf@lechat.rtp-net.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: Glauber Costa <glommer@redhat.com>, qemu-devel@nongnu.org

> > Generally we use tests from ltp testsuite since they have nice tests for most
> > syscalls. However, the testing is not quite systematic, an particularry combinations
> > of host/target glibc appear to create a mess..

> Do you have a list of the syscalls/ltp testcases you're testing ? I've
> made a list, only wants to compare :)

The ltp tests realated syscalls being added/modified in a patch. As said, there is
no systematic "these tests must get through" list used at the moment. perhaps we can
use your list as starters?