From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Autotest mailing list <autotest@test.kernel.org>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: KVM autotest patch queue - All patches worked out
Date: Wed, 17 Jun 2009 02:12:30 -0300 [thread overview]
Message-ID: <1245215551.2943.24.camel@freedom> (raw)
All the patches on the first patch queue e-mail were examined and worked
out. This is a report of the patches that weren't applied yet. Some of
them might not make it into the kvm test, but all of them got follow
ups. Here's the latest report of the patches available:
Patch queue:
--------------------------------------------------------------------------------
David Huff (dhuff@redhat.com)
1) Move kvm functional tests to a 'test' directory
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/26/5812453
I have reworked this patch and made my own version. I need to split it into
smaller patches though.
Reworked, needs review.
--------------------------------------------------------------------------------
Yogi (anantyog@linux.vnet.ibm.com)
1) Support for remote migration
http://kerneltrap.org/mailarchive/linux-kvm/2009/4/30/5607344/thread
I have rebased the patch. However, the patch review and discussion shows that
we want to implement remote migration as a server side test instead of a client
side one. The rebase is just in case we need the patch in the future.
Probably not going to apply, look at a different way to implement the test.
--------------------------------------------------------------------------------
Alexey Eromenko (aeromenk@redhat.com)
1) New test module: iperf
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/31/5840973/thread
Rebase made, made some comments to it.
* The idea of shipping binaries doesn't look very appealing to me
* Autotest already has an iperf test, might be worth a look for linux guests
Pending some issues during review.
--------------------------------------------------------------------------------
Jason Wang (jasowang@redhat.com)
1) TAP network support in kvm-autotest
Michael Goldish has a similar patch to this one, so we need to decide which one
is going to be used. Michael, when possible, please send your patch to support
TAP network on the kvm test.
Need to get a patch from Michael in order to decide which one to apply
(I believe he can merge the good aspects of both into a single patch series).
Thank you very much,
--
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies
reply other threads:[~2009-06-17 5:12 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=1245215551.2943.24.camel@freedom \
--to=lmr@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox