From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: jkosina@suse.cz, masami.hiramatsu.pt@hitachi.com,
hpa@linux.intel.com, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [RFC][PATCH]: x86: clarify/fix no-op barriers for text_poke_bp()
Date: Mon, 31 Jul 2017 11:16:48 -0400 [thread overview]
Message-ID: <20170731111648.6c7d62f2@gandalf.local.home> (raw)
In-Reply-To: <20170731150411.wff4c5qyanv7xtfy@hirez.programming.kicks-ass.net>
On Mon, 31 Jul 2017 17:04:11 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> Well, this is x86, its a NO-OP. The only reason to write barriers like
Is it really a nop?
> that is for documentation purposes and in that regard is confuses. IOW
> has negative value.
Not arguing. But a comment would have helped, even if it was
/* This isn't really needed, but just being paranoid */
-- Steve
next prev parent reply other threads:[~2017-07-31 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:21 Peter Zijlstra
2017-07-31 14:23 ` Steven Rostedt
2017-07-31 15:04 ` Peter Zijlstra
2017-07-31 15:16 ` Steven Rostedt [this message]
2017-07-31 15:26 ` Peter Zijlstra
2017-08-01 9:12 ` Jiri Kosina
2017-08-10 16:42 ` [tip:x86/asm] x86: Clarify/fix " tip-bot for Peter Zijlstra
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=20170731111648.6c7d62f2@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hpa@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=peterz@infradead.org \
--cc=x86@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
all inboxes | Powered by JetHome®