From: Alan Huang <mmpgouride@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, Alan Huang <mmpgouride@gmail.com>
Subject: [PATCH] formal/spinhint: Clarify the proof
Date: Sun, 14 May 2023 14:51:23 +0000 [thread overview]
Message-ID: <20230514145123.37079-1-mmpgouride@gmail.com> (raw)
The third step and the fourth step seem to have no causal relationship between them.
Therefore, this patch explains under what circumstances both counters will be at least 1.
Signed-off-by: Alan Huang <mmpgouride@gmail.com>
---
formal/spinhint.tex | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/formal/spinhint.tex b/formal/spinhint.tex
index 16764aef..dd2e88cc 100644
--- a/formal/spinhint.tex
+++ b/formal/spinhint.tex
@@ -1103,8 +1103,9 @@ follows:
execution.
\item The counter corresponding to this reader will have been
at least 1 during this time interval.
-\item The \co{synchronize_qrcu()} code forces at least one
- of the counters to be at least 1 at all times.
+\item If the counter corresponding to this reader is 1, then
+ the other counter is at least 1 because of the completion of
+ counter flip.
\item Therefore, at any given point in time, either one of the
counters will be at least 2, or both of the counters will
be at least one.
--
2.34.1
next reply other threads:[~2023-05-14 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 14:51 Alan Huang [this message]
2023-05-16 10:07 ` [PATCH] formal/spinhint: Clarify the proof Akira Yokosawa
2023-05-16 10:15 ` Alan Huang
2023-05-17 14:55 ` Akira Yokosawa
2023-05-17 17:02 ` Alan Huang
2023-05-17 19:44 ` Paul E. McKenney
2023-05-21 10:20 ` Paul E. McKenney
2023-05-21 11:35 ` Alan Huang
2023-05-27 10:39 ` Paul E. McKenney
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=20230514145123.37079-1-mmpgouride@gmail.com \
--to=mmpgouride@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).