From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <gregkh@linuxfoundation.org>, <rafael.j.wysocki@intel.com>,
"Alison Schofield" <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <ben.widawsky@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
<nvdimm@lists.linux.dev>
Subject: Re: [PATCH 04/11] cxl/core: Clamp max lock_class
Date: Wed, 9 Mar 2022 18:26:50 +0000 [thread overview]
Message-ID: <20220309182650.00006b28@Huawei.com> (raw)
In-Reply-To: <164610295187.2682974.18123746840987009597.stgit@dwillia2-desk3.amr.corp.intel.com>
On Mon, 28 Feb 2022 18:49:11 -0800
Dan Williams <dan.j.williams@intel.com> wrote:
> MAX_LOCKDEP_SUBCLASSES limits the depth of the CXL topology that can be
> validated by lockdep. Given that the cxl_test topology is already at
> this limit collapse some of the levels and clamp the max depth.
>
> Cc: Alison Schofield <alison.schofield@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Ira Weiny <ira.weiny@intel.com>
> Cc: Ben Widawsky <ben.widawsky@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
> drivers/cxl/cxl.h | 21 +++++++++++++++++----
> 1 file changed, 17 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index 97e6ca7e4940..1357a245037d 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -501,20 +501,33 @@ enum cxl_lock_class {
> CXL_ANON_LOCK,
> CXL_NVDIMM_LOCK,
> CXL_NVDIMM_BRIDGE_LOCK,
I'd be tempted to give explicit value to the one above as well
so it's immediate clear there is deliberate duplication here.
> - CXL_PORT_LOCK,
> + CXL_PORT_LOCK = 2,
> /*
> * Be careful to add new lock classes here, CXL_PORT_LOCK is
> * extended by the port depth, so a maximum CXL port topology
> - * depth would need to be defined first.
> + * depth would need to be defined first. Also, the max
> + * validation depth is limited by MAX_LOCKDEP_SUBCLASSES.
> */
> };
>
> +static inline int clamp_lock_class(struct device *dev, int lock_class)
> +{
> + if (lock_class >= MAX_LOCKDEP_SUBCLASSES) {
> + dev_warn_once(dev,
> + "depth: %d, disabling lockdep for this device\n",
> + lock_class);
> + return 0;
> + }
> +
> + return lock_class;
> +}
> +
> static inline int cxl_lock_class(struct device *dev)
> {
> if (is_cxl_port(dev)) {
> struct cxl_port *port = to_cxl_port(dev);
>
> - return CXL_PORT_LOCK + port->depth;
> + return clamp_lock_class(dev, CXL_PORT_LOCK + port->depth);
> } else if (is_cxl_decoder(dev)) {
> struct cxl_port *port = to_cxl_port(dev->parent);
>
> @@ -522,7 +535,7 @@ static inline int cxl_lock_class(struct device *dev)
> * A decoder is the immediate child of a port, so set
> * its lock class equal to other child device siblings.
> */
> - return CXL_PORT_LOCK + port->depth + 1;
> + return clamp_lock_class(dev, CXL_PORT_LOCK + port->depth + 1);
> } else if (is_cxl_nvdimm_bridge(dev))
> return CXL_NVDIMM_BRIDGE_LOCK;
> else if (is_cxl_nvdimm(dev))
>
next prev parent reply other threads:[~2022-03-09 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 2:48 [PATCH 00/11] device-core: Generic device-lock lockdep validation Dan Williams
2022-03-01 2:48 ` [PATCH 01/11] device-core: Enable " Dan Williams
2022-03-01 2:49 ` [PATCH 02/11] cxl/core: Refactor a cxl_lock_class() out of cxl_nested_lock() Dan Williams
2022-03-09 18:18 ` Jonathan Cameron
2022-03-09 18:34 ` Dan Williams
2022-03-01 2:49 ` [PATCH 03/11] cxl/core: Remove cxl_device_lock() Dan Williams
2022-03-09 18:22 ` Jonathan Cameron
2022-03-10 3:54 ` Dan Williams
2022-03-01 2:49 ` [PATCH 04/11] cxl/core: Clamp max lock_class Dan Williams
2022-03-09 18:26 ` Jonathan Cameron [this message]
2022-03-09 19:59 ` Dan Williams
2022-03-01 2:49 ` [PATCH 05/11] cxl/core: Introduce cxl_set_lock_class() Dan Williams
2022-03-09 18:33 ` Jonathan Cameron
2022-03-10 4:08 ` Dan Williams
2022-03-01 2:49 ` [PATCH 06/11] cxl/acpi: Add a lock class for the root platform device Dan Williams
2022-03-01 2:49 ` [PATCH 07/11] libnvdimm: Refactor an nvdimm_lock_class() helper Dan Williams
2022-03-01 2:49 ` [PATCH 08/11] ACPI: NFIT: Drop nfit_device_lock() Dan Williams
2022-03-01 2:49 ` [PATCH 09/11] libnvdimm: Drop nd_device_lock() Dan Williams
2022-03-01 2:49 ` [PATCH 10/11] libnvdimm: Enable lockdep validation Dan Williams
2022-03-01 2:49 ` [PATCH 11/11] device-core: Introduce a per-subsystem lockdep_mutex Dan Williams
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=20220309182650.00006b28@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rafael.j.wysocki@intel.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