From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Autotest mailing list <autotest@test.kernel.org>
Cc: Lawrence Lim <llim@redhat.com>,
KVM mailing list <kvm@vger.kernel.org>,
Naphtali Sprei <nsprei@redhat.com>
Subject: KVM autotest patch queue report 03-18-2010
Date: Thu, 18 Mar 2010 00:34:01 -0300 [thread overview]
Message-ID: <1268883241.2936.7.camel@localhost.localdomain> (raw)
Once again I'll try to resume the patch queue report for kvm autotest,
since it's a good way to keep folks posted about the status of their
patches. I will figure out some script to extract most of the
information from patchwork, that will allow me to do this with less
effort.
Summary
=======
Total patches: 8
Reviewed patches: 6
Reviews unfinished: 2
Autotest patchwork
http://patchwork.test.kernel.org/project/autotest/list/
--------------------------------------------------------------------------------
[KVM-AUTOTEST] fix tap interface for parallel execution 2010-03-10 yogi lmr Under Review
Michael already explained that in order to enable parallel mode, the
pools have to be modified, not the address_index. So this will be
superseded in favor of a patch that Michael will create.
--------------------------------------------------------------------------------
KVM-Test: Add kvm userspace unit test 2010-03-05 sshang lmr Under review
This patch independs on guest OSs and different qemu command line
scenarios, so we could add it to build.cfg instead of tests_base.cfg.
Discussed this idea and pointed out some better messaging and API usage.
--------------------------------------------------------------------------------
[2/2] KVM test: Add cpu_set subtest 2010-02-25 Lucas Meneghel Rodrigues lmr Under Review
This patch will stay on the queue until the feature tested gets in a
better shape on KVM upstream
--------------------------------------------------------------------------------
KVM test: Add support for ipv6 addresses 2010-02-24 Lucas Meneghel Rodrigues lmr Under Review
This test was reviewed and the decision is that it will stay on the
queue until we have more extensive guest network testing.
--------------------------------------------------------------------------------
KVM test: Memory ballooning test for KVM guest 2010-02-11 pradeep lmr Under Review
Made comments to the patch originator, waiting for a revised version.
--------------------------------------------------------------------------------
KVM-test: Add a subtest 'qemu_img' 2010-01-29 Yolkfull Chow lmr Under Review
Made comments to the patch originator, waiting for a revised version.
--------------------------------------------------------------------------------
[2/2] KVM test: subtest migration: Add rem_host and rem_port for migrate() 2009-12-08 Yolkfull Chow lmr Under Review
[1/2,-,V3] Add a server-side test - kvm_migration 2009-12-08 Yolkfull Chow lmr Under Review
This patchset still needs full review, but remote migration is something
that we want to take slowly, so we can have a first version integrated
upstream with a good round of testing. Right now I am not sure if the
approach on this patchset is the right way of approaching the problem.
reply other threads:[~2010-03-18 3:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1268883241.2936.7.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=llim@redhat.com \
--cc=nsprei@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox