From: Joyce Kong <joyce.kong@arm.com>
To: dts@dpdk.org
Cc: nd@arm.com, Joyce Kong <joyce.kong@arm.com>
Subject: [dts] [PATCH] tests/hello_world: fix invalid_coremask when config RTE_MAX_LCORE
Date: Tue, 5 Jun 2018 13:43:23 +0800 [thread overview]
Message-ID: <1528177403-27939-1-git-send-email-joyce.kong@arm.com> (raw)
Add check for CONFIG_RTE_MAX_LCORE when getting maximum logical core
numbers
Signed-off-by: Joyce Kong <joyce.kong@arm.com>
---
tests/TestSuite_hello_world.py | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_hello_world.py b/tests/TestSuite_hello_world.py
index 1c5934c..7227e13 100644
--- a/tests/TestSuite_hello_world.py
+++ b/tests/TestSuite_hello_world.py
@@ -78,11 +78,24 @@ class TestHelloWorld(TestCase):
# get the maximun logical core number
cores = self.dut.get_core_list('all')
- coreMask = utils.create_mask(cores)
+
+ out = self.dut.send_expect("cat config/defconfig_%s" % self.target, "]# ", 10)
+ start_position = out.find('CONFIG_RTE_MAX_LCORE=')
+
+ if start_position > -1:
+ if out.find('\n', start_position) > -1:
+ end_position = out.find('\n', start_position)
+ else:
+ end_position = len(out)
+ available_max_lcore = int(out[start_position + 21:end_position])
+ else:
+ available_max_lcore = len(cores) + 1
+
+ coreMask = utils.create_mask(cores[:available_max_lcore - 1])
cmdline = "./examples/helloworld/build/app/helloworld -n 1 -c " + coreMask
out = self.dut.send_expect(cmdline, "# ", 50)
- for i in range(len(cores)):
+ for i in range(available_max_lcore - 1):
self.verify("hello from core %s" % cores[i] in out, "EAL not started on core%s" % cores[i])
def tear_down(self):
--
1.8.3.1
next reply other threads:[~2018-06-05 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 5:43 Joyce Kong [this message]
2018-06-11 5:23 ` Liu, Yong
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=1528177403-27939-1-git-send-email-joyce.kong@arm.com \
--to=joyce.kong@arm.com \
--cc=dts@dpdk.org \
--cc=nd@arm.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).