Announcement

Collapse
No announcement yet.

Call Depth Tracking For Less Costly Retbleed Mitigation Hopes To Land Soon

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

  • Call Depth Tracking For Less Costly Retbleed Mitigation Hopes To Land Soon

    Phoronix: Call Depth Tracking For Less Costly Retbleed Mitigation Hopes To Land Soon

    Longtime Linux kernel engineer Peter Zijlstra with Intel has sent out his latest "Call Depth Tracking" patches as a mitigiation for Retbleed that aims to be less costly on system performance than the current mitigation approach. With this latest patch series, he indicates he hopes to soon get this code mainlined...

    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
    Will this be useful for Ryzen CPUs too?

    Comment


    • #3
      Originally posted by xcom View Post
      Will this be useful for Ryzen CPUs too?
      Ryzen already has the "unret" mitigation as default with much lower performance impact than IBRS:

      Comment


      • #4
        Originally posted by xcom View Post

        Will this be useful for Ryzen CPUs too?
        Yes.

        Originally posted by hotaru View Post

        Ryzen already has the "unret" mitigation as default with much lower performance impact than IBRS:
        It is insufficient: https://www.phoronix.com/news/AMD-Li...eed-STIBP-IBPB

        If opting for the more secure Indirect Branch Prediction Barrier "IBPB" mitigation that can mitigate short speculation windows on basic block boundaries too, rather than just the "unret" default, it now turns out a month later Single Thread Indirect Branch Predictors "STIBP" must also be enabled.

        Comment


        • #5
          Michael

          Typo

          "mitigiation" should be "mitigation"

          Comment


          • #6
            I thought these would be fixed in hardware.

            Comment


            • #7
              Originally posted by Mangix View Post
              I thought these would be fixed in hardware.
              Like an Intel engineer coming home to your house and replacing your old CPU?

              Comment


              • #8
                I mean...even newer CPUs have these issues. They have not been fixed in hardware.

                Comment

                Working...
                X