From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: David Wilder <dwilder@us.ibm.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "pradeep@us.ibm.com" <pradeep@us.ibm.com>,
"wilder@us.ibm.com" <wilder@us.ibm.com>
Subject: Re: [dts] [PATCH V1] tests/unit_tests_qos: Add ppc_64 to supported list.
Date: Wed, 3 Apr 2019 17:18:07 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA5B74C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190327212114.1805-1-dwilder@us.ibm.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of David Wilder
> Sent: Wednesday, March 27, 2019 2:21 PM
> To: dts@dpdk.org
> Cc: pradeep@us.ibm.com; wilder@us.ibm.com
> Subject: [dts] [PATCH V1] tests/unit_tests_qos: Add ppc_64 to supported list.
>
> Sched auto_test only supports specific architectures.
> Added ppc_64 to the list and validated on Power9.
>
> Signed-off-by: David Wilder <dwilder@us.ibm.com>
> ---
> tests/TestSuite_unit_tests_qos.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_unit_tests_qos.py
> b/tests/TestSuite_unit_tests_qos.py
> index 20d42a0..a946402 100644
> --- a/tests/TestSuite_unit_tests_qos.py
> +++ b/tests/TestSuite_unit_tests_qos.py
> @@ -95,7 +95,7 @@ class TestUnitTestsQos(TestCase):
> """
>
> [arch, machine, env, toolchain] = self.target.split('-')
> - self.verify(arch in ["x86_64" ,"arm64"], "Sched auto_test only support in
> x86_64 or arm64")
> + self.verify(arch in ["x86_64" ,"arm64" ,"ppc_64"], "Sched auto_test only
> support in x86_64 or arm64 ppc_64")
>
> self.dut.send_expect("./%s/app/test -n 1 -c %s" % (self.target,
> self.coremask), "R.*T.*E.*>.*>", 30)
> out = self.dut.send_expect("sched_autotest", "RTE>>", 5)
> --
> 1.8.3.1
prev parent reply other threads:[~2019-04-03 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 21:21 David Wilder
2019-04-03 17:18 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BA5B74C@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=dwilder@us.ibm.com \
--cc=pradeep@us.ibm.com \
--cc=wilder@us.ibm.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).