From: Lucas Meneghel Rodrigues <lookkas@gmail.com>
To: autotest@test.kernel.org
Cc: aarcange@redhat.com, kvm@vger.kernel.org
Subject: [PATCH 0/3] Transparent Hugepages tests v4
Date: Mon, 27 Jun 2011 13:26:40 -0300 [thread overview]
Message-ID: <1309192003-5456-1-git-send-email-lookkas@gmail.com> (raw)
This patchset comprises tests for the Transparent memory Hugepages
functionality on KVM guests. Included we have common test setup, 4
test cases (smoke, stress, defrag and swapping) and the correspondent
test configuration variants on tests_base.cfg.sample.
After this round of reviews, I believe the test is good for upstream
inclusion. As Andrea is on vacation, I'm going to commit the patchset,
but he's more than welcome to do post-commit review of the tests.
Yiqiao Pu (3):
virt: Add Transparent Hugepages setup
KVM test: Add Transparent Hugepages subtests
Add THP test variants to tests_base.cfg.sample
client/tests/kvm/tests/trans_hugepage.py | 127 ++++++++++++++
client/tests/kvm/tests/trans_hugepage_defrag.py | 86 ++++++++++
client/tests/kvm/tests/trans_hugepage_swapping.py | 115 +++++++++++++
client/tests/kvm/tests_base.cfg.sample | 15 ++
client/virt/virt_test_setup.py | 186 ++++++++++++++++++++-
5 files changed, 528 insertions(+), 1 deletions(-)
create mode 100644 client/tests/kvm/tests/trans_hugepage.py
create mode 100644 client/tests/kvm/tests/trans_hugepage_defrag.py
create mode 100644 client/tests/kvm/tests/trans_hugepage_swapping.py
--
1.7.5.4
next reply other threads:[~2011-06-27 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 16:26 Lucas Meneghel Rodrigues [this message]
2011-06-27 16:26 ` [PATCH 1/3] virt: Add Transparent Hugepages setup Lucas Meneghel Rodrigues
2011-06-27 16:26 ` [PATCH 2/3] KVM test: Add Transparent Hugepages subtests Lucas Meneghel Rodrigues
2011-06-27 16:26 ` [PATCH 3/3] Add THP test variants to tests_base.cfg.sample Lucas Meneghel Rodrigues
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=1309192003-5456-1-git-send-email-lookkas@gmail.com \
--to=lookkas@gmail.com \
--cc=aarcange@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