From: jspewock@iol.unh.edu
To: Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
thomas@monjalon.net, wathsala.vithanage@arm.com,
probb@iol.unh.edu, paul.szczepanek@arm.com
Cc: dev@dpdk.org, Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v1 0/1] dts: Add the ability to bind ports to drivers
Date: Thu, 26 Oct 2023 17:58:57 -0400 [thread overview]
Message-ID: <20231026220059.10685-2-jspewock@iol.unh.edu> (raw)
From: Jeremy Spewock <jspewock@iol.unh.edu>
Currently in the DTS framework there is nothing that allows you to bind
ports on the SUT to different drivers, but the ability to do so is
necessary in the case of many different test suites. This change allows
developers to bind to either os_driver or os_driver_for_dpdk which they
define in conf.yaml.
This patch additionally binds to the driver for DPDK at the
start of each build target setup which means that test suites will be
run on the driver for DPDK unless otherwise specified.
Jeremy Spewock (1):
dts: bind to DPDK driver before running test suites
dts/framework/remote_session/linux_session.py | 3 ++
dts/framework/remote_session/os_session.py | 6 ++++
dts/framework/testbed_model/sut_node.py | 34 +++++++++++++++++++
dts/tests/TestSuite_os_udp.py | 4 +++
dts/tests/TestSuite_smoke_tests.py | 6 ++--
5 files changed, 49 insertions(+), 4 deletions(-)
--
2.42.0
next reply other threads:[~2023-10-26 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 21:58 jspewock [this message]
2023-10-26 21:58 ` [PATCH v1 1/1] dts: bind to DPDK driver before running test suites jspewock
2023-11-08 11:03 ` Juraj Linkeš
2023-11-08 16:38 ` Jeremy Spewock
2023-11-08 16:44 ` Patrick Robb
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=20231026220059.10685-2-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@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).