From: Andrea Parri <parri.andrea@gmail.com>
To: stern@rowland.harvard.edu, will@kernel.org, peterz@infradead.org,
boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
j.alglave@ucl.ac.uk, luc.maranget@inria.fr, paulmck@kernel.org,
akiyks@gmail.com, dlustig@nvidia.com, joel@joelfernandes.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
hernan.poncedeleon@huaweicloud.com,
jonas.oberhauser@huaweicloud.com
Subject: Re: [PATCH] tools/memory-model: Document herd7 (internal) representation
Date: Fri, 24 May 2024 17:37:06 +0200 [thread overview]
Message-ID: <ZlC0IkzpQdeGj+a3@andrea> (raw)
In-Reply-To: <20240524151356.236071-1-parri.andrea@gmail.com>
> - While checking the information below using herd7, I've observed some
> "strange" behavior with spin_is_locked() (perhaps, unsurprisingly...);
> IAC, that's also excluded from this table/submission.
For completeness, the behavior in question:
$ cat T.litmus
C T
{}
P0(spinlock_t *x)
{
int r0;
spin_lock(x);
spin_unlock(x);
r0 = spin_is_locked(x);
}
$ herd7 -conf linux-kernel.cfg T.litmus
Test T Required
States 0
Ok
Witnesses
Positive: 0 Negative: 0
Condition forall (true)
Observation T Never 0 0
Time T 0.00
Hash=6fa204e139ddddf2cb6fa963bad117c0
Haven't been using spin_is_locked for a while... perhaps I'm doing
something wrong? (IAC, will have a closer look next week...)
Andrea
next prev parent reply other threads:[~2024-05-24 15:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 15:13 [PATCH] tools/memory-model: Document herd7 (internal) representation Andrea Parri
2024-05-24 15:37 ` Andrea Parri [this message]
2024-05-24 15:51 ` Alan Stern
2024-05-24 15:55 ` Andrea Parri
2024-05-24 20:04 ` Alan Stern
2024-05-25 19:37 ` Alan Stern
2024-05-27 8:07 ` Andrea Parri
2024-06-05 15:31 ` Alan Stern
2024-06-05 17:05 ` Andrea Parri
2024-06-05 19:26 ` Andrea Parri
2024-06-05 19:40 ` Alan Stern
2024-05-27 13:16 ` Jonas Oberhauser
2024-05-24 15:53 ` Alan Stern
2024-05-24 16:00 ` Andrea Parri
2024-05-27 12:25 ` Hernan Ponce de Leon
2024-05-27 13:14 ` Jonas Oberhauser
2024-05-27 13:32 ` Andrea Parri
2024-05-27 13:33 ` Alan Stern
2024-05-27 12:22 ` Hernan Ponce de Leon
2024-05-27 13:28 ` Andrea Parri
2024-05-27 13:37 ` Alan Stern
2024-05-27 13:47 ` Jonas Oberhauser
2024-05-27 13:40 ` Jonas Oberhauser
2024-05-28 17:58 ` Boqun Feng
2024-05-29 12:37 ` Jonas Oberhauser
2024-05-29 14:07 ` Alan Stern
2024-05-29 14:17 ` Jonas Oberhauser
2024-05-29 14:24 ` Alan Stern
2024-05-29 14:33 ` Jonas Oberhauser
2024-05-27 17:57 ` Hernan Ponce de Leon
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=ZlC0IkzpQdeGj+a3@andrea \
--to=parri.andrea@gmail.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=hernan.poncedeleon@huaweicloud.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=jonas.oberhauser@huaweicloud.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@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