From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Ingo Molnar <mingo@kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC] x86: enforce inlining for atomics
Date: Wed, 29 Apr 2015 22:52:46 -0300 [thread overview]
Message-ID: <20150430015246.GD14218@khazad-dum.debian.net> (raw)
In-Reply-To: <CAPh34memztvm3mF+o+QO-ocu9NG7o_z-Uf+0VtVneet0CJoB9A@mail.gmail.com>
On Wed, 22 Apr 2015, Hagen Paul Pfeifer wrote:
> On 22 April 2015 at 11:28, Ingo Molnar <mingo@kernel.org> wrote:
> > So I think the original patch makes sense (and I already applied it),
> > we want known-simple and performance critical methods (such as atomic
> > ops) always inlined.
>
> Right. As I wrote I will post a follow up patch for the remaining
> cases where inline is a must. To guarantee that performance critical
> functions are always inlined - no matter what configuration is used.
It would be nice to see those patches in -stable eventually, please...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2015-04-30 1:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 21:27 Hagen Paul Pfeifer
2015-04-20 21:56 ` Borislav Petkov
2015-04-20 22:08 ` Hagen Paul Pfeifer
2015-04-21 7:42 ` Ingo Molnar
2015-04-21 10:56 ` Hagen Paul Pfeifer
2015-04-21 22:57 ` Hagen Paul Pfeifer
2015-04-22 0:57 ` Linus Torvalds
2015-04-22 5:24 ` Markus Trippelsdorf
2015-04-22 5:58 ` Hagen Paul Pfeifer
2015-04-22 9:20 ` Markus Trippelsdorf
2015-04-22 9:28 ` Ingo Molnar
2015-04-22 9:31 ` Hagen Paul Pfeifer
2015-04-30 1:52 ` Henrique de Moraes Holschuh [this message]
2015-07-13 18:27 ` Denys Vlasenko
2015-07-13 19:20 ` Hagen Paul Pfeifer
2015-07-13 21:06 ` Denys Vlasenko
2015-07-13 21:12 ` Hagen Paul Pfeifer
2015-07-13 18:25 ` Denys Vlasenko
2015-04-20 23:46 ` Peter Zijlstra
2015-04-22 14:10 ` [tip:x86/asm] x86/asm: Always inline atomics tip-bot for Hagen Paul Pfeifer
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=20150430015246.GD14218@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hagen@jauu.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome