Chandler Carruth via llvm-dev
2018-Jan-04 10:23 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
Sending a note here as this seems likely to be of relatively broad interest. Thread: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20180101/513630.html Review link: https://reviews.llvm.org/D41723# -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180104/78682480/attachment.html>
Alex Bradbury via llvm-dev
2018-Jan-04 14:20 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
On 4 January 2018 at 10:23, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org> wrote:> Sending a note here as this seems likely to be of relatively broad interest. > > Thread: > http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20180101/513630.html > > Review link: > https://reviews.llvm.org/D41723#It seems the review link is getting wider coverage (Reddit, HN, ...) and Phabricator is struggling under the load. Best, Alex
Chandler Carruth via llvm-dev
2018-Jan-04 16:49 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
The folks working on phab are busily propping it up. It should be relatively healthy now. On Thu, Jan 4, 2018 at 9:20 AM Alex Bradbury via llvm-dev < llvm-dev at lists.llvm.org> wrote:> On 4 January 2018 at 10:23, Chandler Carruth via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Sending a note here as this seems likely to be of relatively broad > interest. > > > > Thread: > > > http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20180101/513630.html > > > > Review link: > > https://reviews.llvm.org/D41723# > > It seems the review link is getting wider coverage (Reddit, HN, ...) > and Phabricator is struggling under the load. > > Best, > > Alex > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180104/98a8df01/attachment-0001.html>
Stephen Checkoway via llvm-dev
2018-Jan-04 17:30 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
> On Jan 4, 2018, at 04:23, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Sending a note here as this seems likely to be of relatively broad interest.It looks like this is producing code of the following form. call next loop: pause jmp loop next: mov [rsp], r11 ret As I understand it, the busy loop is to cause the speculative execution to be trapped in the loop. Was something like ud2 considered? I presume that would stop the speculative execution without involving any of the execution units the way the busy loop does. -- Stephen Checkoway
Chandler Carruth via llvm-dev
2018-Jan-04 17:52 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
On Thu, Jan 4, 2018 at 12:31 PM Stephen Checkoway via llvm-dev < llvm-dev at lists.llvm.org> wrote:> > > On Jan 4, 2018, at 04:23, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Sending a note here as this seems likely to be of relatively broad > interest. > > It looks like this is producing code of the following form. > > call next > loop: > pause > jmp loop > next: > mov [rsp], r11 > ret > > As I understand it, the busy loop is to cause the speculative execution to > be trapped in the loop. Was something like ud2 considered? I presume that > would stop the speculative execution without involving any of the execution > units the way the busy loop does. >The pause instruction will also avoid tying up execution resources in speculative contexts, so I wouldn't expect it to be significantly different.> > -- > Stephen Checkoway > > > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180104/e51f6309/attachment.html>
Kristof Beyls via llvm-dev
2018-Jan-05 11:15 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
Thanks for the notification, Chandler. I also wanted to note that I’ve just posted another component for Spectre mitigation (variant 1), see https://reviews.llvm.org/D41760 and https://reviews.llvm.org/D41761. I believe this is completely complementary to the retpoline mitigation you pointed to at https://reviews.llvm.org/D41723#, which is targeted at mitigating variant 2. Thanks, Kristof On 4 Jan 2018, at 11:23, Chandler Carruth via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: Sending a note here as this seems likely to be of relatively broad interest. Thread: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20180101/513630.html Review link: https://reviews.llvm.org/D41723# _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180105/fdd26bf1/attachment.html>
Chandler Carruth via llvm-dev
2018-Jan-05 11:22 UTC
[llvm-dev] FYI, we've posted a component of Spectre mitigation on llvm-commits
Awesome, replied. We've been working on similar things, but didn't have them ready-to-publish due to slightly lower urgency (there are reasonable ways to locally mimic these kinds of things in sensitive areas like the Linux kernel, and even finding code patterns for variant #1 is substantially harder). We have some significantly different APIs we'd like to discuss here based on experience trying to implement these on x86 and deploy them to a reasonably large body of code. Hopefully more details soon as folks have time. On Fri, Jan 5, 2018 at 6:15 AM Kristof Beyls <Kristof.Beyls at arm.com> wrote:> Thanks for the notification, Chandler. > > I also wanted to note that I’ve just posted another component for Spectre > mitigation (variant 1), see https://reviews.llvm.org/D41760 and > https://reviews.llvm.org/D41761. > I believe this is completely complementary to the retpoline mitigation you > pointed to at https://reviews.llvm.org/D41723#, which is targeted at > mitigating variant 2. > > Thanks, > > Kristof > > On 4 Jan 2018, at 11:23, Chandler Carruth via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Sending a note here as this seems likely to be of relatively broad > interest. > > Thread: > > http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20180101/513630.html > > Review link: > https://reviews.llvm.org/D41723# > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180105/df1e55c7/attachment.html>
Maybe Matching Threads
- FYI, we've posted a component of Spectre mitigation on llvm-commits
- FYI, we've posted a component of Spectre mitigation on llvm-commits
- FYI, we've posted a component of Spectre mitigation on llvm-commits
- FYI, we've posted a component of Spectre mitigation on llvm-commits
- RFC: Speculative Load Hardening (a Spectre variant #1 mitigation)