All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	jmerkey@wolfmountaingroup.com,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: [ANNOUNCE] mdb: Merkey's Linux Kernel Debugger 	2.6.27-rc4	released
Date: Thu, 21 Aug 2008 19:21:40 +0300	[thread overview]
Message-ID: <48AD9614.6060701@qumranet.com> (raw)
In-Reply-To: <1219327799.8651.134.camel@twins>

Peter Zijlstra wrote:
> Not sure - I think all barrier clobber the full register and memory set.
> So if you access a variable after a barrier it will have to issue a
> load.
>   

IIRC a barrier only clobbers memory.  gcc must reload a variable from 
memory unless it can prove the variable's address has not escaped anywhere.

So:

void f()
{
    int v;

    v = g();
    barrier();
    do_domething_with(v);
}

Need not reload v from memory (indeed, v can be in a register for its 
entire lifetime), but

void f()
{
    int v;

    v = g();
    h(&v);
    barrier();
    do_domething_with(v);
}
 
Will force v into memory, and reload it after the barrier.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-08-21 16:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  2:50 [ANNOUNCE] mdb: Merkey's Linux Kernel Debugger 2.6.27-rc4 released jmerkey
2008-08-21 10:07 ` Peter Zijlstra
2008-08-21 10:57   ` Stefan Richter
2008-08-21 11:02     ` Peter Zijlstra
2008-08-21 11:47       ` Paul E. McKenney
2008-08-21 12:03         ` Peter Zijlstra
2008-08-21 14:53           ` Paul E. McKenney
2008-08-21 14:58             ` jmerkey
2008-08-21 12:05         ` Stefan Richter
2008-08-21 12:26           ` jmerkey
     [not found]             ` <43593.166.70.238.46.1219321595.squirrel@webmail.wolfmountaingroup.com >
2008-08-21 12:35               ` jmerkey
2008-08-21 13:37             ` Nick Piggin
2008-08-21 14:09               ` Stefan Richter
2008-08-22  1:40                 ` Nick Piggin
2008-08-22  6:32                   ` Stefan Richter
2008-08-22 11:54                     ` jmerkey
2008-08-22 12:36                       ` Stefan Richter
2008-08-21 14:09               ` Peter Zijlstra
2008-08-21 14:30                 ` Paul E. McKenney
2008-08-21 14:14                   ` jmerkey
2008-08-21 14:48                   ` Peter Zijlstra
2008-08-21 16:21                 ` Avi Kivity [this message]
2008-08-21 21:06               ` Jeremy Fitzhardinge
2008-08-21 21:18                 ` Linus Torvalds
2008-08-21 21:21                   ` Jeremy Fitzhardinge
2008-08-24  4:25                   ` jmerkey
2008-08-26  8:26                     ` Andi Kleen
2008-08-27  1:49                       ` jmerkey
2008-08-22  1:37                 ` Nick Piggin
2008-08-21 14:02             ` Stefan Richter
2008-08-21 14:08               ` jmerkey
2008-08-21 15:22                 ` Stefan Richter
2008-08-21 15:02                   ` jmerkey
2008-08-21 15:57         ` Linus Torvalds
2008-08-21 16:18           ` Linus Torvalds
2008-08-21 16:48             ` Paul E. McKenney
2008-09-24  0:01               ` Paul E. McKenney
2008-08-21 16:43           ` 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=48AD9614.6060701@qumranet.com \
    --to=avi@qumranet.com \
    --cc=dhowells@redhat.com \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.