public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Peter Zijlstra <peterz@infradead.org>,
	parri.andrea@gmail.com, will.deacon@arm.com,
	boqun.feng@gmail.com, npiggin@gmail.com, dhowells@redhat.com,
	j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
	linux-kernel@vger.kernel.org, elena.reshetova@intel.com
Subject: Re: Prototype patch for Linux-kernel memory model
Date: Fri, 22 Dec 2017 09:41:32 +0530	[thread overview]
Message-ID: <20171222041132.GA5354@afzalpc> (raw)
In-Reply-To: <20171221161502.GX7829@linux.vnet.ibm.com>

Hi,

On Thu, Dec 21, 2017 at 08:15:02AM -0800, Paul E. McKenney wrote:
> On Thu, Dec 21, 2017 at 09:00:55AM +0530, afzal mohammed wrote:

> > Since it is now mentioned that r1 can have final value of 0, though it
> > is understood, it might make things crystal clear and for the sake of
> > completeness to also show the non-automatic variable x being
> > initialized to 0.
> 
> Here we rely on the C-language and Linux-kernel convention that global
> variables that are not explicitly initialized are initialized to zero.
> (Also the documented behavior of the litmus tests and the herd tool that
> uses them.)  So that part should be OK as is.

Okay, that was suggested to bring parity with some of the examples in
explanation.txt, where global variables are explicitly initalized to
zero, that unconsciously made me feel that litmus tests also follow
that pattern, but checking again realize that litmus tests are not so.

> 
> Nevertheless, thank you for your review and comments!

Thanks for taking the effort to reply.

> Have you installed and run the herd tool?  Doing so would allow you
> to experiment with changes to the litmus tests.

Yes, i installed herd tool and then i was at a loss :(, so started
re-reading the documentation, yet to run any of the tests.

afzal

  reply	other threads:[~2017-12-22  4:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 18:40 Prototype patch for Linux-kernel memory model Paul E. McKenney
2017-11-13 20:09 ` Alan Stern
2017-11-14  4:52   ` Paul E. McKenney
2017-11-14  7:59 ` Peter Zijlstra
2017-11-14 15:19   ` Alan Stern
2017-11-14 17:15     ` Paul E. McKenney
2017-11-15 16:37       ` Paul E. McKenney
2017-11-17 11:27         ` Boqun Feng
2017-11-20 16:35           ` Andrea Parri
2017-11-20 19:30             ` Paul E. McKenney
2017-12-19  8:36         ` afzal mohammed
2017-12-19 16:05           ` Alan Stern
2017-12-20 11:31         ` afzal mohammed
2017-12-20 16:45           ` Paul E. McKenney
2017-12-21  3:30             ` afzal mohammed
2017-12-21 16:15               ` Paul E. McKenney
2017-12-22  4:11                 ` afzal mohammed [this message]
2017-12-23  6:14                   ` afzal mohammed
2018-01-02 20:25                     ` 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=20171222041132.GA5354@afzalpc \
    --to=afzal.mohd.ma@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=elena.reshetova@intel.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=will.deacon@arm.com \
    /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