From: Steven Rostedt <rostedt@goodmis.org>
To: Jason Baron <jbaron@redhat.com>
Cc: Glauber Costa <glommer@parallels.com>,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
Tejun Heo <tj@kernel.org>,
kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org,
devel@openvz.org, Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v4 1/3] make jump_labels wait while updates are in place
Date: Fri, 27 Apr 2012 10:07:10 -0400 [thread overview]
Message-ID: <1335535630.28106.209.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120427135320.GA13762@redhat.com>
On Fri, 2012-04-27 at 09:53 -0400, Jason Baron wrote:
> Right, for x86 which uses stop_machine currently, we guarantee that all
> cpus are going to see the updated code, before the inc of key->enabled.
> However, other arches (sparc, mips, powerpc, for example), seem to be
> using much lighter weight updates, which I hope are ok :)
And x86 will soon be removing stop_machine() from its path too. But all
archs should perform some kind of memory sync after patching code. Thus
the update should be treated as if a memory barrier was added after it,
and before the inc.
-- Steve
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-27 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 22:51 [PATCH v4 0/3] fix problem with static_branch() for sock memcg Glauber Costa
2012-04-26 22:51 ` [PATCH v4 1/3] make jump_labels wait while updates are in place Glauber Costa
2012-04-27 0:43 ` Steven Rostedt
2012-04-27 1:05 ` KAMEZAWA Hiroyuki
2012-04-27 13:53 ` Jason Baron
2012-04-27 14:07 ` Steven Rostedt [this message]
2012-04-27 14:59 ` Glauber Costa
2012-04-26 22:51 ` [PATCH v4 2/3] Always free struct memcg through schedule_work() Glauber Costa
2012-04-26 22:51 ` [PATCH v4 3/3] decrement static keys on real destroy time Glauber Costa
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=1335535630.28106.209.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=cgroups@vger.kernel.org \
--cc=devel@openvz.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=jbaron@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tj@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