Announcement

Collapse
No announcement yet.

Arm CPUs Hit By Straight Line Speculation Vulnerability, LLVM Adds Initial Mitigation

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Arm CPUs Hit By Straight Line Speculation Vulnerability, LLVM Adds Initial Mitigation

    Phoronix: Arm CPUs Hit By Straight Line Speculation Vulnerability, LLVM Adds Initial Mitigation

    While Intel's CrossTalk/SRBDS vulnerability dominated the conversation on Tuesday, Arm quietly revealed a new speculative execution vulnerability of its own called Straight Line Speculation...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Wonder how long before we start seeing the AMD vulnerabilities ...

    Comment


    • #3
      Originally posted by Raka555 View Post
      Wonder how long before we start seeing the AMD vulnerabilities ...
      You can be sure that Intel is pouring support into groups researching AMD CPU's for hardware vulnerabilities..

      Comment


      • #4
        How will this affect Amazon ARM thing?

        Comment


        • #5
          No, no, no. According to Intel haters, only Intel has vulnerabilities and all others are 100% safe. I call fake news.

          (just kidding )

          Comment


          • #6
            Due to performance costs involved, Arm hasn't yet endorsed enabling such compiler mitigations by default and encourages compiler developers to look at the possibility of per-function overrides and similar options.
            according to the whitepaper, there shouldn't be much performance cost at all:

            While a DSB+ISB sequence is expected to have a significantly greater impact on performance than an SB if architecturally executed, in many of the cases outlined in this document the DSB+ISB sequence is not architecturally executed and should have no direct impact on performance save for a reduction in code density. Secondary effects may include marginally increased pressures on the instruction caches and branch predictors.

            Comment

            Working...
            X