From: Alison Schofield <alison.schofield@intel.com>
To: Li Ming <ming.li@zohomail.com>
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] cxl/hdm: Verify HDM decoder capabilities after parsing
Date: Thu, 27 Feb 2025 13:47:21 -0800 [thread overview]
Message-ID: <Z8DdafbX6_tbM4DW@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250227103251.390147-1-ming.li@zohomail.com>
On Thu, Feb 27, 2025 at 06:32:51PM +0800, Li Ming wrote:
> devm_cxl_setup_hdm() only checks if decoder_count is 0 after parsing HDM
> decoder capability, But according to the implementation of
> cxl_hdm_decoder_count(), cxlhdm->decoder_count will never be 0.
How does a check against the spec maximums benefit this driver? Is there
a bad path we avoid by checking and quitting at this point.
Might this catch silly decoder counts that the driver previously
ignored?
>
> Per CXL specification, the values ranges of decoder_count and
> target_count are limited. Adding a checking for the values of them
> in case hardware initialized them with wrong values.
Similar question - is this catching something sooner, rather than
later?
>
> Signed-off-by: Li Ming <ming.li@zohomail.com>
> ---
> base-commit: 22eea823f69ae39dc060c4027e8d1470803d2e49 cxl/next
> ---
> drivers/cxl/core/hdm.c | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/core/hdm.c b/drivers/cxl/core/hdm.c
> index 70cae4ebf8a4..a98191867c22 100644
> --- a/drivers/cxl/core/hdm.c
> +++ b/drivers/cxl/core/hdm.c
> @@ -138,6 +138,34 @@ static bool should_emulate_decoders(struct cxl_endpoint_dvsec_info *info)
> return true;
> }
>
> +static int cxlhdm_decoder_caps_verify(struct cxl_hdm *cxlhdm)
> +{
> + /*
> + * CXL r3.2 section 8.2.4.20.1
> + * CXL devices shall not advertise more than 10 decoders,
> + * CXL switches and HBs may advertise up to 32 decoders.
> + */
> + if (is_cxl_endpoint(cxlhdm->port) && cxlhdm->decoder_count > 10)
> + return -EINVAL;
> + else if (cxlhdm->decoder_count > 32)
> + return -EINVAL;
> +
> + /*
> + * CXL r3.2 section 8.2.4.20.1
> + * target count is applicable only to CXL upstream port and HB.
> + * The number of target ports each decoder supports should be
> + * one of the numbers 1, 2, 4 or 8.
> + */
> + if (!is_cxl_endpoint(cxlhdm->port) &&
> + cxlhdm->target_count != 1 &&
> + cxlhdm->target_count != 2 &&
> + cxlhdm->target_count != 4 &&
> + cxlhdm->target_count != 8)
> + return -EINVAL;
Maybe instead of manual bitwise checks try
(!is_power_of_2(cxlhdm->target_count) || cxlhdm->target_count > 8))
> +
> + return 0;
> +}
> +
> /**
> * devm_cxl_setup_hdm - map HDM decoder component registers
> * @port: cxl_port to map
> @@ -182,7 +210,8 @@ struct cxl_hdm *devm_cxl_setup_hdm(struct cxl_port *port,
> }
>
> parse_hdm_decoder_caps(cxlhdm);
> - if (cxlhdm->decoder_count == 0) {
> + rc = cxlhdm_decoder_caps_verify(cxlhdm);
> + if (rc) {
> dev_err(dev, "Spec violation. Caps invalid\n");
Can you move the dev_err to the verify function and include the
specific invalid capability.
--Alison
> return ERR_PTR(-ENXIO);
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-02-27 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 10:32 [PATCH v1 1/1] cxl/hdm: Verify HDM decoder capabilities after parsing Li Ming
2025-02-27 15:21 ` Dave Jiang
2025-02-28 2:48 ` Li Ming
2025-02-27 21:47 ` Alison Schofield [this message]
2025-02-28 2:47 ` Li Ming
2025-02-28 18:34 ` Alison Schofield
2025-02-28 23:45 ` Dan Williams
2025-03-01 3:00 ` Li Ming
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=Z8DdafbX6_tbM4DW@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--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