From: Borislav Petkov <bp@alien8.de>
To: Scotty Bauer <sbauer@eng.utah.edu>
Cc: tglx@linutronix.de, mingo@redheat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/smpboot: check if CLFLUSH is actually necessary
Date: Fri, 6 Feb 2015 17:05:47 +0100 [thread overview]
Message-ID: <20150206160547.GF3220@pd.tnic> (raw)
In-Reply-To: <20150130233142.GA1884@pd.tnic>
On Sat, Jan 31, 2015 at 12:31:42AM +0100, Borislav Petkov wrote:
> asm volatile(ALTERNATIVE(ASM_NOP3, "clflush %[p]", X86_BUG_CLFLUSH_MONITOR)
> : [p] "+m" (*mwait_ptr));
>
> Totally untested though - it is supposed to show the idea only.
Yeah, here's a working diff, ontop of this patchset:
https://lkml.kernel.org/r/1422987390-17878-1-git-send-email-bp@alien8.de
---
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 6d7022c683e3..771ebd6e8b77 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1432,7 +1432,11 @@ static inline void mwait_play_dead(void)
* case where we return around the loop.
*/
mb();
- clflush(mwait_ptr);
+
+ asm volatile(ALTERNATIVE("", "clflush %[p]",
+ X86_BUG_CLFLUSH_MONITOR)
+ : [p] "+m" (*(unsigned long *)mwait_ptr));
+
mb();
__monitor(mwait_ptr, 0, 0);
mb();
--
At build time you have:
--
...
ffffffff81038dcc: 65 48 8b 1c 25 88 ab mov %gs:0xab88,%rbx # movq %gs:kernel_stack,%rbx #, pfo_ret__
ffffffff81038dd3: 00 00
ffffffff81038dd5: 48 81 eb c8 3f 00 00 sub $0x3fc8,%rbx # subq $16328, %rbx #, mwait_ptr
ffffffff81038ddc: 0f 09 wbinvd
ffffffff81038dde: 45 31 e4 xor %r12d,%r12d
ffffffff81038de1: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
ffffffff81038de8: 0f ae f0 mfence
ffffffff81038deb: 90 nop
ffffffff81038dec: 90 nop
ffffffff81038ded: 90 nop
ffffffff81038dee: 0f ae f0 mfence
ffffffff81038df1: 48 89 d8 mov %rbx,%rax
...
--
which during runtime, on those affected machines only, gets patched to:
---
...
ffffffff81038dcc: mov %gs:0xab88,%rbx
ffffffff81038dd5: sub $0x3fc8,%rbx
ffffffff81038ddc: wbinvd
ffffffff81038dde: xor %r12d,%r12d
ffffffff81038de1: nopl 0x0(%rax)
ffffffff81038de8: mfence
ffffffff81038deb: clflush (%rbx) <---
ffffffff81038dee: mfence
ffffffff81038df1: mov %rbx,%rax
...
---
:-)
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-02-06 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 21:26 [PATCH] x86/smpboot: check if CLFLUSH is actually necessary Scotty Bauer
2015-01-30 23:31 ` Borislav Petkov
2015-02-06 16:05 ` Borislav Petkov [this message]
2015-02-06 16:13 ` [PATCH] x86, smpboot: Call CLFLUSH only on X86_BUG_CLFLUSH_MONITOR-affected CPUs Borislav Petkov
2015-02-11 18:39 ` Scotty Bauer
2015-02-11 20:25 ` Borislav Petkov
2015-02-11 21:55 ` [PATCH] x86/smpboot: check if CLFLUSH is actually necessary H. Peter Anvin
2015-02-11 21:55 ` H. Peter Anvin
2015-02-11 23:10 ` Scotty Bauer
2015-02-12 9:16 ` Borislav Petkov
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=20150206160547.GF3220@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redheat.com \
--cc=sbauer@eng.utah.edu \
--cc=tglx@linutronix.de \
--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