• Barbecue Cowboy@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    19
    arrow-down
    7
    ·
    12 hours ago

    It feels weird this was even ever a standard consumer feature. I wouldn’t even really expect it on enterprise hardware outside of servers. This feels like stuff you only really need to think about if you’re being directly targeted by a group with resources.

      • Barbecue Cowboy@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        4 hours ago

        I mean yeah maybe, this one is focused on protecting from threat actors with physical access which is kind of another level.

    • raldone01@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      10 hours ago

      It seems like it is not a lot of overhead if any at all. Also the hardware design easily accommodates it. So why not if the work is already done?

      • tempest@lemmy.ca
        link
        fedilink
        English
        arrow-up
        11
        ·
        10 hours ago

        There is still some overhead. Enough that if you are doing HPC and running on your own hardware you might want want to disable it.

        I’ve disabled it on epycs for this reason but never touched it on ryzens.