[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0d3428c2-6a3c-4d71-bc4d-057ba926852b@linux.ibm.com>
Date: Wed, 4 Jun 2025 19:25:42 +0530
From: Sourabh Jain <sourabhjain@...ux.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Max Kellermann <max.kellermann@...os.com>
Cc: song@...nel.org, joel.granados@...nel.org, dianders@...omium.org,
cminyard@...sta.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] kernel/rcu/tree_stall: add
/sys/kernel/rcu_stall_count
On 04/06/25 05:46, Andrew Morton wrote:
> On Tue, 3 Jun 2025 22:09:30 +0530 Sourabh Jain <sourabhjain@...ux.ibm.com> wrote:
>
>> Hello Andrew,
>>
>>> +#endif
>>> +
>>> rcu_stall_notifier_call_chain(RCU_STALL_NOTIFY_NORM, (void *)j - gps);
>>> if (READ_ONCE(csd_lock_suppress_rcu_stall) && csd_lock_is_stuck()) {
>>> pr_err("INFO: %s detected stall, but suppressed full report due to a stuck CSD-lock.\n", rcu_state.name);
>> It seems like this patch was not applied properly to the upstream tree.
>>
>> Out of the three hunks in this patch, only the first one is applied; the
>> second
>> and third hunks are missing.
>>
>> commit 2536c5c7d6ae5e1d844aa21f28b326b5e7f815ef
>> Author: Max Kellermann <max.kellermann@...os.com>
>> Date: Sun May 4 20:08:31 2025 +0200
>>
>> kernel/rcu/tree_stall: add /sys/kernel/rcu_stall_count
>>
>> Expose a simple counter to userspace for monitoring tools.
> OK. iirc there was quite a lot of churn and conflicts here :)
>
> Please send a fixup against latest -linus?
Sure, I will wait for a day or two to see if Max is interested in
sending the fix-up patch. Otherwise, I will send it.
Thanks,
Sourabh Jain
Powered by blists - more mailing lists