• oce 🐆@jlai.lu
    link
    fedilink
    English
    arrow-up
    18
    ·
    22 hours ago

    The point is the Linux Kernel is covering the same security mitigations which make the CPU level ones redundant. If all users are using the Linux Kernel, why would it be an issue?

    • 9tr6gyp3@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      edit-2
      22 hours ago

      Depends on how you use your system if you have multiple users. CPU mitigations wont protect GPU workloads, and vice versa. If your CPU was mitigating GPU workloads, that would probably be a massive performance loss.

      • Cypher@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        21 hours ago

        That’s not how this works.

        The vulnerability is all on the CPU side. The GPU workloads being referenced are only vulnerable on the CPU instruction set used to pass workloads to the GPU.

        Talking about CPU and GPU workloads as entirely separate in this context is misleading as the vulnerability is with CPU code execution that passes tasks to the GPU.

        The GPU is not vulnerable to this particular attack, only the CPU is.

        As you can see here impacted hardware is all CPU side, you can also read about how the proposed attacks work.

        https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/spectre.html

        • 9tr6gyp3@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          17 hours ago

          Forgive me. Just trying to understand. How does the kernel flag NEO_DISABLE_MITIGATIONS have any affect on the CPU? Seems to be targeted towards OpenCL and Level Zero, which are APIs to access GPU hardware directly.