From: Amos Kong <akong@redhat.com>
To: jzupka <jzupka@redhat.com>
Cc: autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] BUG: Turnoff khugepaged before start tests
Date: Thu, 19 Aug 2010 10:59:21 +0800 [thread overview]
Message-ID: <20100819025915.GA4093@z> (raw)
In-Reply-To: <1282084805-1485-1-git-send-email-jzupka@redhat.com>
On Tue, Aug 17, 2010 at 06:40:05PM -0400, jzupka wrote:
> ---
> client/tests/kvm/tests/ksm_overcommit.py | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
Looks good for me. Except some trailing whitespace :)
After disable transparent hugepage, ksm_parallel can pass.
ksm_serial always fail of 'copy_files_to failed', but single file transfer test can pass.
Lucas, do you touch this kind of problem ?
> diff --git a/client/tests/kvm/tests/ksm_overcommit.py b/client/tests/kvm/tests/ksm_overcommit.py
> index 2b49a65..b8bee42 100644
> --- a/client/tests/kvm/tests/ksm_overcommit.py
> +++ b/client/tests/kvm/tests/ksm_overcommit.py
> @@ -367,11 +367,16 @@ def run_ksm_overcommit(test, params, env):
>
> # Main test code
> logging.info("Starting phase 0: Initialization")
> - new_ksm = False
> + new_ksm = False
> if (os.path.exists("/sys/kernel/mm/ksm/run")):
> utils.run("echo 50 > /sys/kernel/mm/ksm/sleep_millisecs")
> utils.run("echo 5000 > /sys/kernel/mm/ksm/pages_to_scan")
> utils.run("echo 1 > /sys/kernel/mm/ksm/run")
> +
> + if (os.path.exists("/sys/kernel/mm/transparent_hugepage/enabled")):
> + utils.run("echo 'never' > /sys/kernel/mm/transparent_hugepage/enabled ")
> + if (os.path.exists("/sys/kernel/mm/redhat_transparent_hugepage/enabled")):
> + utils.run("echo 'never' > /sys/kernel/mm/redhat_transparent_hugepage/enabled ")
> new_ksm = True
> else:
> try:
> --
> 1.6.5.2
>
next prev parent reply other threads:[~2010-08-19 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 22:40 [PATCH] BUG: Turnoff khugepaged before start tests jzupka
2010-08-19 2:59 ` Amos Kong [this message]
2010-08-20 20:37 ` 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=20100819025915.GA4093@z \
--to=akong@redhat.com \
--cc=autotest@test.kernel.org \
--cc=jzupka@redhat.com \
--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 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.