From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection
Date: Mon, 24 May 2021 13:00:29 +0900 [thread overview]
Message-ID: <YKsk3ZdDyoy9/Ga/@google.com> (raw)
In-Reply-To: <20210524034645.GH4441@paulmck-ThinkPad-P17-Gen-1>
On (21/05/23 20:46), Paul E. McKenney wrote:
>
> In theory, yes, sort of, anyway. In practice, highly unlikely.
> The most plausible way for this to happen is for this code path to be
> delayed for a long time on a 32-bit system, so that jiffies+ULONG_MAX/2
> actually arrives. But in that case, all sorts of other complaints
> would happen first.
I see.
> But I could make this a cmpxchg(), if that is what you are getting at.
No, it's good. I was just curious what scenario I was missing.
next prev parent reply other threads:[~2021-05-24 4:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 15:56 [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection Sergey Senozhatsky
2021-05-21 15:56 ` [PATCH 2/2] rcu: do not disable gp stall detection in rcu_cpu_stall_reset() Sergey Senozhatsky
2021-05-21 18:01 ` [PATCHv2 1/2] rcu/tree: handle VM stoppage in stall detection Paul E. McKenney
2021-05-21 21:38 ` Paul E. McKenney
2021-05-24 1:56 ` Sergey Senozhatsky
2021-05-24 3:46 ` Paul E. McKenney
2021-05-24 4:00 ` Sergey Senozhatsky [this message]
2021-07-15 9:09 ` Sergey Senozhatsky
2021-07-15 13:32 ` Paul E. McKenney
2021-07-15 14:08 ` Sergey Senozhatsky
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=YKsk3ZdDyoy9/Ga/@google.com \
--to=senozhatsky@chromium.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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