qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on confi


From: Rtp
Subject: Re: [Qemu-devel] [PATCH 2/2] check for utimensat() availability on configure
Date: Thu, 11 Jun 2009 10:33:12 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Riku Voipio <address@hidden> writes:
Hi,

> On Wed, Jun 10, 2009 at 01:56:40PM -0300, Glauber Costa wrote:
>> > >> because mainline qemu is lacking a linux-user maintainer.
>> > > I believe if you can guarantee (through proper testing) the stability of 
>> > > maemo
>> > > tree, and poke for review the specific parts that may affect the rest ot 
>> > > the world,
>> > > then it should be fine to just pull it.
>
>> > At least, this would be better than what we have currently. Please note
>> > also that "proper testing" is hard imho. It depends also on host/guest
>> > systems used to test.
>
>> it is hard for everybody, not just qemu user. Since you guys are the main
>> user of it, if you are happy with the state of things, and it is isolated 
>> enough from
>> the rest of qemu not to break it very frequently, we should be fine.
>
> 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 :)

>
> That said, the changes are highly contained under linux-user/, in the current 
> tree
> there is only one patch (GUEST_BASE support) that touches outside parts.
>
>> > Having an "official" maintainer means having someone being able to give
>> > his final word if people disagree on how to fix a bug.
>
>> One of you should step up and do it.
>
> If nobody objects, I can.

I bet you have more time than me to work on qemu so that's
fine. Nevertheless, I can provide help if needed.


Arnaud




reply via email to

[Prev in Thread] Current Thread [Next in Thread]