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 report 03-12-2009
Date: Thu, 03 Dec 2009 01:32:44 -0200 [thread overview]
Message-ID: <1259811164.3827.6.camel@localhost.localdomain> (raw)
Patch: Major control file cleanup
URL: http://patchwork.test.kernel.org/patch/1464/
Comments: Will split this work in 2 stages:
• Cleanups and splitting kvm_tests.cfg in a "base config" + "test
definitions"
• Move "test definitions" to control file then having an utility to
parse all config and generate the nice dictionaries for the whole test
Status: Need work
Patch: KSM ovecommit test v.2
URL: http://patchwork.test.kernel.org/patch/1529/
Comments: Dor made initial comments on the patchset, I still need to
review it myself
Status: Pending review
Patch: Add PCI device assignment support
URL: http://patchwork.test.kernel.org/patch/1554/
Comments: I've re-spin this patch and asked for revision, got some
comments from the original author, will implement them. In general, need
people with appropriate hardware (that can do SR-IOV) to test if VF
testing works as expected.
Status: Pending testing
Patch: Adding download of .au3 tests to autoit subtest
URL: http://patchwork.test.kernel.org/patch/1558/
Comments: I am concerned about the variant defaults, that rely on git
under windows.
Status: Need to get from author some details about functionality usage.
Patch: Add a server-side test: kvm_migration
URL: http://patchwork.test.kernel.org/patch/1569/
Comments: Implements the much awaited KVM remote migration as a server
side test. Need to review it appropriately.
Status: Pending review
reply other threads:[~2009-12-03 3:32 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=1259811164.3827.6.camel@localhost.localdomain \
--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