From: Andi Kleen <ak@linux.jf.intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Eli Friedman <eli.friedman@gmail.com>,
Jim Grosbach <grosbach@apple.com>,
Stephen Checkoway <s@pahtak.org>, LLVMdev <llvmdev@cs.uiuc.edu>
Subject: Re: [PATCH] x86/asm: avoid mnemonics without type suffix
Date: Sun, 14 Jul 2013 14:14:46 -0700 [thread overview]
Message-ID: <20130714211446.GP5643@tassilo.jf.intel.com> (raw)
In-Reply-To: <51E2FAB9.9050900@goop.org>
I think best would be to just find some way to implement LOCK prefix
patching using atomic compiler intrinsics and then switch to those
Then all this inline assembler horror could be ifdef'ed away
for old compilers only, and likely the generated code would
be better as the compiler could optimize more.
Or just give up on LOCK patching, as single CPU systems
and VMs are less and less interesting?
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-07-14 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 12:56 [PATCH] x86/asm: avoid mnemonics without type suffix Ramkumar Ramachandra
2013-07-14 17:19 ` Linus Torvalds
2013-07-14 18:26 ` Ramkumar Ramachandra
2013-07-14 18:34 ` Linus Torvalds
2013-07-14 18:49 ` Ramkumar Ramachandra
2013-07-14 18:35 ` [LLVMdev] " Tim Northover
2013-07-14 19:09 ` Linus Torvalds
2013-07-14 19:30 ` Tim Northover
2013-07-14 19:41 ` Jeremy Fitzhardinge
2013-07-14 19:49 ` Linus Torvalds
2013-07-15 18:40 ` H. Peter Anvin
2013-07-15 18:56 ` Linus Torvalds
2013-07-15 19:00 ` H. Peter Anvin
2013-07-15 19:00 ` Linus Torvalds
2013-07-14 19:23 ` Jeremy Fitzhardinge
2013-07-14 19:29 ` Linus Torvalds
2013-07-15 18:40 ` H. Peter Anvin
2013-07-14 19:23 ` Jeremy Fitzhardinge
2013-07-14 21:14 ` Andi Kleen [this message]
2013-07-15 18:42 ` H. Peter Anvin
2013-07-15 18:47 ` H. Peter Anvin
2013-07-15 18:58 ` Linus Torvalds
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=20130714211446.GP5643@tassilo.jf.intel.com \
--to=ak@linux.jf.intel.com \
--cc=artagnon@gmail.com \
--cc=eli.friedman@gmail.com \
--cc=grosbach@apple.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvmdev@cs.uiuc.edu \
--cc=mingo@kernel.org \
--cc=s@pahtak.org \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox