From: Alison Schofield <alison.schofield@intel.com>
To: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: [NDCTL PATCH v2] cxl: Change cxl-topology.sh assumption on host bridge validation
Date: Wed, 14 May 2025 12:20:52 -0700 [thread overview]
Message-ID: <aCTtFOKwurphnMOJ@aschofie-mobl2.lan> (raw)
In-Reply-To: <1a69ac7c-7a8e-4351-b07f-642b39208c84@fujitsu.com>
On Wed, May 14, 2025 at 06:58:45AM +0000, Zhijian Li (Fujitsu) wrote:
>
>
> On 09/05/2025 04:44, Dave Jiang wrote:
> > Current host bridge validation in cxl-topology.sh assumes that the
> > decoder enumeration is in order and therefore the port numbers can
> > be used as a sorting key. With delayed port enumeration, this
> > assumption is no longer true. Change the sorting to by number
> > of children ports for each host bridge as the test code expects
> > the first 2 host bridges to have 2 children and the third to only
> > have 1.
> >
> > Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
>
> It seems it's a bit later, anyway
>
> Tested-by: Li Zhijian <lizhijian@fujitsu.com>
Thanks! I'll pick up your tag if I rebase pending. (probably will ;))
>
>
> > ---
> > v2:
> > - Merged Vishal's suggestion
> >
> > test/cxl-topology.sh | 31 +++++++++++++++++++++++++++----
> > 1 file changed, 27 insertions(+), 4 deletions(-)
> >
> > diff --git a/test/cxl-topology.sh b/test/cxl-topology.sh
> > index 90b9c98273db..49e919a187af 100644
> > --- a/test/cxl-topology.sh
> > +++ b/test/cxl-topology.sh
> > @@ -37,15 +37,37 @@ root=$(jq -r ".[] | .bus" <<< $json)
> >
> >
> > # validate 2 or 3 host bridges under a root port
> > -port_sort="sort_by(.port | .[4:] | tonumber)"
> > json=$($CXL list -b cxl_test -BP)
> > count=$(jq ".[] | .[\"ports:$root\"] | length" <<< $json)
> > ((count == 2)) || ((count == 3)) || err "$LINENO"
> > bridges=$count
> >
> > -bridge[0]=$(jq -r ".[] | .[\"ports:$root\"] | $port_sort | .[0].port" <<< $json)
> > -bridge[1]=$(jq -r ".[] | .[\"ports:$root\"] | $port_sort | .[1].port" <<< $json)
> > -((bridges > 2)) && bridge[2]=$(jq -r ".[] | .[\"ports:$root\"] | $port_sort | .[2].port" <<< $json)
> > +bridge_filter()
> > +{
> > + local br_num="$1"
> > +
> > + jq -r \
> > + --arg key "$root" \
> > + --argjson br_num "$br_num" \
> > + '.[] |
> > + select(has("ports:" + $key)) |
> > + .["ports:" + $key] |
> > + map(
> > + {
> > + full: .,
> > + length: (.["ports:" + .port] | length)
> > + }
> > + ) |
> > + sort_by(-.length) |
> > + map(.full) |
> > + .[$br_num].port'
> > +}
> > +
> > +# $count has already been sanitized for acceptable values, so
> > +# just collect $count bridges here.
> > +for i in $(seq 0 $((count - 1))); do
> > + bridge[$i]="$(bridge_filter "$i" <<< "$json")"
> > +done
> >
> > # validate root ports per host bridge
> > check_host_bridge()
> > @@ -64,6 +86,7 @@ json=$($CXL list -b cxl_test -P -p ${bridge[0]})
> > count=$(jq ".[] | .[\"ports:${bridge[0]}\"] | length" <<< $json)
> > ((count == 2)) || err "$LINENO"
> >
> > +port_sort="sort_by(.port | .[4:] | tonumber)"
> > switch[0]=$(jq -r ".[] | .[\"ports:${bridge[0]}\"] | $port_sort | .[0].host" <<< $json)
> > switch[1]=$(jq -r ".[] | .[\"ports:${bridge[0]}\"] | $port_sort | .[1].host" <<< $json)
> >
> >
> > base-commit: 01eeaf2954b2c3ff52622d62fdae1c18cd15ab66
prev parent reply other threads:[~2025-05-14 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 20:44 [NDCTL PATCH v2] cxl: Change cxl-topology.sh assumption on host bridge validation Dave Jiang
2025-05-14 0:50 ` Alison Schofield
2025-05-14 6:58 ` Zhijian Li (Fujitsu)
2025-05-14 19:20 ` Alison Schofield [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=aCTtFOKwurphnMOJ@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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