From: Dean Marx <dmarx@iol.unh.edu>
To: Nicholas Pratte <npratte@iol.unh.edu>
Cc: yoan.picchi@foss.arm.com, luca.vizzarro@arm.com,
probb@iol.unh.edu, paul.szczepanek@arm.com,
Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
jspewock@iol.unh.edu, alex.chapman@arm.com, dev@dpdk.org
Subject: Re: [PATCH v1 1/3] dts: rework port attributes in config module
Date: Tue, 29 Oct 2024 12:52:42 -0400 [thread overview]
Message-ID: <CABD7UXOq77Zucp+sOTmLHRnVFng_a5EzTQduUS5toj2BdzEF9g@mail.gmail.com> (raw)
In-Reply-To: <20240821184305.28028-3-npratte@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Wed, Aug 21, 2024 at 2:43 PM Nicholas Pratte <npratte@iol.unh.edu> wrote:
> The current design requires that a peer pci port is identified so that
> test suites can create the correct port links. While this can work, it
> also creates a lot of room for user error. Instead, devices should be
> given a unique identifier which is referenced in defined test runs.
>
> Both defined testbeds for the SUT and TG must have an equal number of
> specified ports. In each given array or ports, SUT port 0 is connected
> to TG port 0, SUT port 1 is connected to TG port 1, etc.
>
> Bugzilla ID: 1478
>
> Signed-off-by: Nicholas Pratte <npratte@iol.unh.edu>
>
Aside from Jeremy/Juraj's comments and assuming this will get extended off
the pydantic series:
Reviewed-by: Dean Marx <dmarx@iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 1251 bytes --]
next prev parent reply other threads:[~2024-10-29 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 18:43 [PATCH v1 0/3] dts: rework topology definition in dts config Nicholas Pratte
2024-08-21 18:43 ` [PATCH v1 1/3] dts: rework port attributes in config module Nicholas Pratte
2024-09-04 18:18 ` Jeremy Spewock
2024-09-10 10:11 ` Juraj Linkeš
2024-10-29 16:52 ` Dean Marx [this message]
2024-08-21 18:43 ` [PATCH v1 2/3] dts: rework testbed_model Port objects to contain unique identifiers Nicholas Pratte
2024-09-04 18:18 ` Jeremy Spewock
2024-09-10 10:17 ` Juraj Linkeš
2024-10-29 16:53 ` Dean Marx
2024-08-21 18:43 ` [PATCH v1 3/3] dts: rework test suite and dts runner to include test_run configs Nicholas Pratte
2024-09-04 18:18 ` Jeremy Spewock
2024-09-10 11:05 ` Juraj Linkeš
2024-09-27 14:38 ` Jeremy Spewock
2024-10-29 17:00 ` Dean Marx
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=CABD7UXOq77Zucp+sOTmLHRnVFng_a5EzTQduUS5toj2BdzEF9g@mail.gmail.com \
--to=dmarx@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=npratte@iol.unh.edu \
--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).