DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicholas Pratte <npratte@iol.unh.edu>
To: Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com,
	luca.vizzarro@arm.com, juraj.linkes@pantheon.tech,
	bruce.richardson@intel.com, jspewock@iol.unh.edu,
	probb@iol.unh.edu, dmarx@iol.unh.edu, yoan.picchi@foss.arm.com
Cc: dev@dpdk.org, Nicholas Pratte <npratte@iol.unh.edu>
Subject: [PATCH 0/4] dts: Remove Excess Attributes From User Config
Date: Thu, 13 Jun 2024 16:18:26 -0400	[thread overview]
Message-ID: <20240613201831.9748-3-npratte@iol.unh.edu> (raw)

A good amount of the attributes listed in the conf.yaml are either
currently unused or unneeded. The goal of this patch is to eliminate
minutiea from the config that may make the overall execution process
more difficult and tedious.

It should be noted that more improvements are possible here, and
in fact, there are other improvements that can likely be made in the
future; for instance, the removal of the OS attribute, and simplication
of the port topology listings (this is currently being worked on in a
separate patch). If it is desired, and the others are okay with it,
I'd like to look into potentially getting rid of the OS attribute at
some point.

Nicholas Pratte (4):
  dts: Remove build target config and list of devices
  dts: Use First Core Logic Change
  dts: Self-Discovering Architecture Change
  dts: Rework DPDK Attributes In SUT Node Config

 doc/guides/tools/dts.rst                     |  24 +---
 dts/conf.yaml                                |  26 ++--
 dts/framework/config/__init__.py             |  76 ++++------
 dts/framework/config/conf_yaml_schema.json   | 144 ++++---------------
 dts/framework/config/types.py                |  38 ++---
 dts/framework/runner.py                      |   2 +-
 dts/framework/test_result.py                 |  14 +-
 dts/framework/testbed_model/cpu.py           |   5 +
 dts/framework/testbed_model/linux_session.py |   5 +-
 dts/framework/testbed_model/node.py          |  20 +--
 dts/framework/testbed_model/os_session.py    |  10 +-
 dts/framework/testbed_model/posix_session.py |   6 +
 dts/framework/testbed_model/sut_node.py      |  25 ++--
 13 files changed, 125 insertions(+), 270 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-06-13 20:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 20:18 Nicholas Pratte [this message]
2024-06-13 20:18 ` [PATCH 1/4] dts: Remove build target config and list of devices Nicholas Pratte
2024-06-14 18:07   ` Jeremy Spewock
2024-06-13 20:18 ` [PATCH 2/4] dts: Use First Core Logic Change Nicholas Pratte
2024-06-14 18:09   ` Jeremy Spewock
2024-06-20 13:41     ` Nicholas Pratte
2024-06-13 20:18 ` [PATCH 3/4] dts: Self-Discovering Architecture Change Nicholas Pratte
2024-06-14 18:09   ` Jeremy Spewock
2024-06-13 20:18 ` [PATCH 4/4] dts: Rework DPDK Attributes In SUT Node Config Nicholas Pratte
2024-06-14 18:11   ` Jeremy Spewock

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=20240613201831.9748-3-npratte@iol.unh.edu \
    --to=npratte@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmarx@iol.unh.edu \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=yoan.picchi@foss.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).