From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bjorn Andersson <andersson@kernel.org>,
linux-remoteproc@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [PATCH v2 0/4] hwspinlock: add summary in debugfs
Date: Mon, 29 Jun 2026 12:03:34 +0200 [thread overview]
Message-ID: <akJC9pD2b5GQbB0u@ninjato> (raw)
In-Reply-To: <ajk_u7TVT-kL8z2A@casper.infradead.org>
> The hwspinlock_tree_lock is not needed as the
> spinlock built into the XArray is sufficient for all these cases.
Are you sure about this?
In hwspin_lock_request_specific(), the spinlock is taken, then:
hwspin_lock_request_specific()
-> __hwspin_lock_request()
-> pm_runtime_get_sync()
-> __pm_runtime_resume()
This starts with:
might_sleep_if(!(rpmflags & RPM_ASYNC) && !dev->power.irq_safe &&
dev->power.runtime_status != RPM_ACTIVE);
Isn't this a problem?
prev parent reply other threads:[~2026-06-29 10:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:51 [PATCH v2 0/4] hwspinlock: add summary in debugfs Wolfram Sang
2026-06-22 8:52 ` [PATCH v2 1/4] radix-tree: add parameter doc for radix_tree_deref_slot_protected() Wolfram Sang
2026-06-22 10:16 ` Andy Shevchenko
2026-06-22 8:52 ` [PATCH v2 2/4] radix-tree: allow more lock types with radix_tree_deref_slot_protected() Wolfram Sang
2026-06-22 10:18 ` Andy Shevchenko
2026-06-22 8:52 ` [PATCH v2 3/4] hwspinlock: annotate slot pointer as RCU sensitive Wolfram Sang
2026-06-22 10:20 ` Andy Shevchenko
2026-06-29 9:07 ` Wolfram Sang
2026-06-22 8:52 ` [PATCH v2 4/4] hwspinlock: add summary in debugfs Wolfram Sang
2026-06-22 10:24 ` Andy Shevchenko
2026-06-22 13:59 ` [PATCH v2 0/4] " Matthew Wilcox
2026-06-22 16:20 ` Wolfram Sang
2026-06-29 8:57 ` Wolfram Sang
2026-06-29 10:40 ` Andy Shevchenko
2026-06-29 10:55 ` Wolfram Sang
2026-06-29 18:54 ` Matthew Wilcox
2026-07-01 15:07 ` Wolfram Sang
2026-06-29 10:03 ` Wolfram Sang [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=akJC9pD2b5GQbB0u@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andersson@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=willy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.