All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: kvm@vger.kernel.org, Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 0/1] integrate qemu-test into kvm-userspace
Date: Tue, 29 Jul 2008 16:17:59 +0300	[thread overview]
Message-ID: <488F1887.5000807@qumranet.com> (raw)
In-Reply-To: <1217004805-13955-1-git-send-email-ryanh@us.ibm.com>

Ryan Harper wrote:
> This patch provides a relatively simple method for exercising various
> features of qemu/kvm by interacting with the guest via serial and qemu
> via the monitor that individual developers can use to validate that
> their changes having broken fundamental feature/function.  Such tests
> need to be very accessable and easy-to-use to encourge there use by
> users/developers.  As a bonus, in-tree make test is trivially integrated
> into higher-level test frameworks such as autotest.
>
>   

The downside of this is that it effectively makes me the qemu-test 
maintainer, which will degrade my response times further.  Also, I have 
no real understanding of this code base.

I would really prefer an independent testsuite maintainer to pick this up.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 0/1] integrate qemu-test into kvm-userspace
Date: Tue, 29 Jul 2008 16:17:59 +0300	[thread overview]
Message-ID: <488F1887.5000807@qumranet.com> (raw)
In-Reply-To: <1217004805-13955-1-git-send-email-ryanh@us.ibm.com>

Ryan Harper wrote:
> This patch provides a relatively simple method for exercising various
> features of qemu/kvm by interacting with the guest via serial and qemu
> via the monitor that individual developers can use to validate that
> their changes having broken fundamental feature/function.  Such tests
> need to be very accessable and easy-to-use to encourge there use by
> users/developers.  As a bonus, in-tree make test is trivially integrated
> into higher-level test frameworks such as autotest.
>
>   

The downside of this is that it effectively makes me the qemu-test 
maintainer, which will degrade my response times further.  Also, I have 
no real understanding of this code base.

I would really prefer an independent testsuite maintainer to pick this up.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2008-07-29 13:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 16:53 [PATCH 0/1] integrate qemu-test into kvm-userspace Ryan Harper
2008-07-25 16:53 ` [Qemu-devel] " Ryan Harper
2008-07-25 16:53 ` [PATCH 1/1] " Ryan Harper
2008-07-25 16:53   ` [Qemu-devel] " Ryan Harper
2008-07-25 17:12 ` [Qemu-devel] [PATCH 0/1] " Paul Brook
2008-07-25 17:12   ` Paul Brook
2008-07-25 17:52   ` Anthony Liguori
2008-07-25 17:52     ` Anthony Liguori
2008-07-25 17:57   ` Ryan Harper
2008-07-25 17:57     ` Ryan Harper
2008-07-29 13:17 ` Avi Kivity [this message]
2008-07-29 13:17   ` [Qemu-devel] " Avi Kivity

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=488F1887.5000807@qumranet.com \
    --to=avi@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ryanh@us.ibm.com \
    /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.