[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZlC0IkzpQdeGj+a3@andrea>
Date: Fri, 24 May 2024 17:37:06 +0200
From: Andrea Parri <parri.andrea@...il.com>
To: stern@...land.harvard.edu, will@...nel.org, peterz@...radead.org,
boqun.feng@...il.com, npiggin@...il.com, dhowells@...hat.com,
j.alglave@....ac.uk, luc.maranget@...ia.fr, paulmck@...nel.org,
akiyks@...il.com, dlustig@...dia.com, joel@...lfernandes.org
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
hernan.poncedeleon@...weicloud.com,
jonas.oberhauser@...weicloud.com
Subject: Re: [PATCH] tools/memory-model: Document herd7 (internal)
representation
> - 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
Powered by blists - more mailing lists