From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: autotest@test.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Autotest] [PATCH] KVM test: Add subtest nmi_watchdog
Date: Tue, 26 Jul 2011 15:31:54 -0300 [thread overview]
Message-ID: <4E2F081A.2000600@redhat.com> (raw)
In-Reply-To: <1311704702-25973-1-git-send-email-lmr@redhat.com>
On 07/26/2011 03:25 PM, Lucas Meneghel Rodrigues wrote:
> From: Amos Kong<akong@redhat.com>
>
> Uses kernel supported nmi_watchdog to test the nmi support of kvm,
> check the nmi count in Linux platform through /proc/interrupts.
Hi Amos, applied your test, thanks!
> Changes from v2:
> * Updated the test to use more current KVM autotest API
>
> Signed-off-by: Amos Kong<akong@redhat.com>
> ---
> client/tests/kvm/tests/nmi_watchdog.py | 60 ++++++++++++++++++++++++++++++++
> client/tests/kvm/tests_base.cfg.sample | 7 ++++
> 2 files changed, 67 insertions(+), 0 deletions(-)
> create mode 100644 client/tests/kvm/tests/nmi_watchdog.py
>
> diff --git a/client/tests/kvm/tests/nmi_watchdog.py b/client/tests/kvm/tests/nmi_watchdog.py
> new file mode 100644
> index 0000000..a4b2349
> --- /dev/null
> +++ b/client/tests/kvm/tests/nmi_watchdog.py
> @@ -0,0 +1,60 @@
> +import time, logging
> +from autotest_lib.client.common_lib import error
> +
> +
> +@error.context_aware
> +def run_nmi_watchdog(test, params, env):
> + """
> + Test the function of nmi injection and verify the response of guest
> +
> + 1) Log in the guest
> + 2) Add 'watchdog=1' to boot option
> + 2) Check if guest's NMI counter augment after injecting nmi
> +
> + @param test: kvm test object
> + @param params: Dictionary with the test parameters.
> + @param env: Dictionary with test environment.
> + """
> + vm = env.get_vm(params["main_vm"])
> + vm.verify_alive()
> + timeout=int(params.get("login_timeout", 360))
> + session = vm.wait_for_login(timeout=timeout)
> + get_nmi_cmd= params.get("get_nmi_cmd")
> + kernel_version = session.get_command_output("uname -r").strip()
> + nmi_watchdog_type = int(params.get("nmi_watchdog_type"))
> + update_kernel_cmd = ("grubby --update-kernel=/boot/vmlinuz-%s "
> + "--args='nmi_watchdog=%d'" %
> + (kernel_version, nmi_watchdog_type))
> +
> + error.context("Add 'nmi_watchdog=%d' to guest kernel cmdline and reboot"
> + % nmi_watchdog_type)
> + session.cmd(update_kernel_cmd)
> + time.sleep(int(params.get("sleep_before_reset", 10)))
> + session = vm.reboot(session, method='shell', timeout=timeout)
> + try:
> + error.context("Getting guest's number of vcpus")
> + guest_cpu_num = session.cmd(params.get("cpu_chk_cmd"))
> +
> + error.context("Getting guest's NMI counter")
> + output = session.cmd(get_nmi_cmd)
> + logging.debug(output.strip())
> + nmi_counter1 = output.split()[1:]
> +
> + logging.info("Waiting 60 seconds to see if guest's NMI counter "
> + "increases")
> + time.sleep(60)
> +
> + error.context("Getting guest's NMI counter 2nd time")
> + output = session.cmd(get_nmi_cmd)
> + logging.debug(output.strip())
> + nmi_counter2 = output.split()[1:]
> +
> + error.context("")
> + for i in range(int(guest_cpu_num)):
> + logging.info("vcpu: %s, nmi_counter1: %s, nmi_counter2: %s" %
> + (i, nmi_counter1[i], nmi_counter2[i]))
> + if int(nmi_counter2[i])<= int(nmi_counter1[i]):
> + raise error.TestFail("Guest's NMI counter did not increase "
> + "after 60 seconds")
> + finally:
> + session.close()
> diff --git a/client/tests/kvm/tests_base.cfg.sample b/client/tests/kvm/tests_base.cfg.sample
> index b7342bd..d597b52 100644
> --- a/client/tests/kvm/tests_base.cfg.sample
> +++ b/client/tests/kvm/tests_base.cfg.sample
> @@ -1108,6 +1108,13 @@ variants:
> cdrom_cd1 = orig.iso
> max_times = 20
>
> + - nmi_watchdog: install setup image_copy unattended_install.cdrom
> + type = nmi_watchdog
> + get_nmi_cmd = grep NMI /proc/interrupts
> + nmi_watchdog_type = 1
> + image_snapshot = yes
> + only Linux
> +
>
> # NICs
> variants:
prev parent reply other threads:[~2011-07-26 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 18:25 [PATCH] KVM test: Add subtest nmi_watchdog Lucas Meneghel Rodrigues
2011-07-26 18:31 ` Lucas Meneghel Rodrigues [this message]
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=4E2F081A.2000600@redhat.com \
--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