From: Mark Brown <broonie@kernel.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/5] regmap: Improve lock handling with maple tree
Date: Thu, 22 Aug 2024 20:13:34 +0100 [thread overview]
Message-ID: <20240822-b4-regmap-maple-nolock-v1-0-d5e6dbae3396@kernel.org> (raw)
The lockdep asserts in the maple tree code and the double locking that
we're doing continue to cause issues, most recently some warnings
reported by Cristian Ciocaltea due to dynamic cache allocations in
interrupt context (which are an issue in themselves, but still). Let's
start trying to improve the situation by configuring the regmap lock as
an external lock for maple tree, allowing it to do it's asserts without
having a separate lock.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (5):
maple_tree: Allow external locks to be configured with their map
regmap: Hold the regmap lock when allocating and freeing the cache
regmap: Use locking during kunit tests
regmap: Wrap maple tree locking
regmap: Don't double lock maple cache when using a regmap provided lock
drivers/base/regmap/internal.h | 12 +++++++++++
drivers/base/regmap/regcache-maple.c | 41 +++++++++++++++++++++++++++---------
drivers/base/regmap/regcache.c | 4 ++++
drivers/base/regmap/regmap-kunit.c | 2 --
drivers/base/regmap/regmap.c | 5 +++++
include/linux/maple_tree.h | 3 +++
6 files changed, 55 insertions(+), 12 deletions(-)
---
base-commit: 7c626ce4bae1ac14f60076d00eafe71af30450ba
change-id: 20240814-b4-regmap-maple-nolock-11408d2d0d41
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2024-08-25 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 19:13 Mark Brown [this message]
2024-08-22 19:13 ` [PATCH 1/5] maple_tree: Allow external locks to be configured with their map Mark Brown
2024-08-22 19:21 ` Matthew Wilcox
2024-08-22 19:48 ` Mark Brown
2024-08-22 19:55 ` Matthew Wilcox
2024-08-22 20:45 ` Mark Brown
2024-08-22 19:13 ` [PATCH 2/5] regmap: Hold the regmap lock when allocating and freeing the cache Mark Brown
[not found] ` <CGME20240828100239eucas1p2afc0d3088c66468061baf81c5676882a@eucas1p2.samsung.com>
2024-08-28 10:02 ` Marek Szyprowski
2024-08-28 11:32 ` Mark Brown
2024-08-22 19:13 ` [PATCH 3/5] regmap: Use locking during kunit tests Mark Brown
2024-08-22 19:13 ` [PATCH 4/5] regmap: Wrap maple tree locking Mark Brown
2024-08-22 19:13 ` [PATCH 5/5] regmap: Don't double lock maple cache when using a regmap provided lock Mark Brown
2024-08-23 22:57 ` (subset) [PATCH 0/5] regmap: Improve lock handling with maple tree Mark Brown
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=20240822-b4-regmap-maple-nolock-v1-0-d5e6dbae3396@kernel.org \
--to=broonie@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
/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).