From: Andi Kleen <andi@firstfloor.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org,
pjt@google.com, torvalds@linux-foundation.org,
gregkh@linux-foundation.org, peterz@infradead.org,
luto@amacapital.net, thomas.lendacky@amd.com,
arjan.van.de.ven@intel.com
Subject: Re: Improve retpoline for Skylake
Date: Fri, 12 Jan 2018 11:21:26 -0800 [thread overview]
Message-ID: <20180112192126.su2evwfefdfeaa6g@two.firstfloor.org> (raw)
In-Reply-To: <1515784373.22302.492.camel@infradead.org>
>
> Skylake still loses if it takes an SMI, right?
SMMs are usually rare, especially on servers, and are usually
not very predictible, and even if you have
one it would need to interrupt on a quite narrow window, so difficult
to arrange. I don't worry about SMM.
> Or encounters a call
> stack of more than 16 in depth?
Yes that's it. This could be mitigated over time.
-Andi
next prev parent reply other threads:[~2018-01-12 19:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 18:45 Improve retpoline for Skylake Andi Kleen
2018-01-12 18:45 ` [PATCH 1/4] x86/retpoline: Add new mode RETPOLINE_UNDERFLOW Andi Kleen
2018-01-12 22:13 ` Dominik Brodowski
2018-01-12 22:57 ` Andi Kleen
2018-01-12 18:45 ` [PATCH 2/4] x86/retpoline: Avoid return buffer underflows on context switch Andi Kleen
2018-01-12 18:45 ` [PATCH 3/4] x86/retpoline: Fill return buffer after idle Andi Kleen
2018-01-12 18:45 ` [PATCH 4/4] x86/retpoline: Fill return buffer on interrupt return to kernel Andi Kleen
2018-01-12 19:12 ` Improve retpoline for Skylake David Woodhouse
2018-01-12 19:21 ` Andi Kleen [this message]
2018-01-12 22:03 ` Henrique de Moraes Holschuh
2018-01-15 8:26 ` Jon Masters
2018-01-15 9:06 ` David Woodhouse
2018-01-15 10:03 ` Thomas Gleixner
2018-01-15 10:20 ` David Woodhouse
2018-01-15 16:57 ` Andy Lutomirski
2018-01-15 17:38 ` Andrew Cooper
2018-01-15 17:56 ` Van De Ven, Arjan
2018-01-15 18:06 ` Andy Lutomirski
2018-01-15 18:07 ` David Woodhouse
2018-01-15 18:10 ` Andy Lutomirski
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=20180112192126.su2evwfefdfeaa6g@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=arjan.van.de.ven@intel.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.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