From: Lijuan Tu <lijuan.tu@intel.com>
To: "zhao,meijuan" <meijuanx.zhao@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH V1] tests/ vm power mgr : fix separator error
Date: Mon, 30 Jul 2018 18:37:34 +0800 [thread overview]
Message-ID: <f008cfaa-916e-236e-089d-8a5d3ac14305@intel.com> (raw)
In-Reply-To: <1532914659-102795-1-git-send-email-meijuanx.zhao@intel.com>
Applied, thanks
On 2018年07月30日 09:37, zhao,meijuan wrote:
> fix separator error
>
> Signed-off-by: zhao,meijuan <meijuanx.zhao@intel.com>
> ---
> tests/TestSuite_vm_power_manager.py | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/tests/TestSuite_vm_power_manager.py b/tests/TestSuite_vm_power_manager.py
> index 4fba2b0..59043c6 100644
> --- a/tests/TestSuite_vm_power_manager.py
> +++ b/tests/TestSuite_vm_power_manager.py
> @@ -114,7 +114,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> """
> # check Channels and vcpus
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = self.vm_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
> self.vm_dut.send_expect("quit", "# ")
>
> @@ -133,7 +133,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> Check host cpu frequency can scale down in VM
> """
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = self.vm_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
>
> for vcpu in range(self.core_num):
> @@ -163,7 +163,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> Check host cpu frequency can scale up in VM
> """
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = self.vm_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
>
> for vcpu in range(self.core_num):
> @@ -190,7 +190,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> Check host cpu frequency can scale to max in VM
> """
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = self.vm_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
>
> max_freq_path = "cat /sys/devices/system/cpu/cpu%s/cpufreq/" + \
> @@ -213,7 +213,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> Check host cpu frequency can scale to min in VM
> """
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = self.vm_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
>
> min_freq_path = "cat /sys/devices/system/cpu/cpu%s/cpufreq/" + \
> @@ -278,7 +278,7 @@ class TestVmPowerManager(TestCase, IxiaPacketGenerator):
> self.verify("No such" not in out, "Compilation error")
>
> guest_cmd = self.vm_power_dir + \
> - "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" %s self.vm_name
> + "guest_cli/build/guest_vm_power_mgr -c 0xf -n 4 -- --vm-name=%s --vcpu-list=0,1,2,3" % self.vm_name
> out = vm2_dut.send_expect(guest_cmd, "vmpower\(guest\)>", 120)
> vm2_dut.send_expect("quit", "# ")
> vm2.stop()
prev parent reply other threads:[~2018-07-30 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 1:37 zhao,meijuan
2018-07-30 10:37 ` Lijuan Tu [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=f008cfaa-916e-236e-089d-8a5d3ac14305@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=meijuanx.zhao@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).