I hate to beat an old horse but am wondering if the latest intel-microcode mitigates the issues with what I think Microsoft calls MDS.
I am running Buster on one drive and Bullseye on two other drives. I have hyper-threading turned off in the bios on my Gigabyte motherboard and implemented mitigations=auto,nosmt in grub on my Intel NUC. I don't play "games" and use the NUC mostly for watching videos. I don't seem to have any issues streaming videos but just wonder if it is safe to enable hyper-threading, and even more would I really benefit from doing so?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Is hyper-threading still an issue
- stevepusser
- Posts: 12930
- Joined: 2009-10-06 05:53
- Has thanked: 41 times
- Been thanked: 71 times
Re: Is hyper-threading still an issue
Experts worry mostly about attacks coming over the Net. If you're not connected, there's not much to worry about.
Many consider it inherently insecure if you are connected, though.
Many consider it inherently insecure if you are connected, though.
MX Linux packager and developer
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: Is hyper-threading still an issue
Enable SMT from the firmware ("BIOS") setting and ask the kernel what it thinks:ticojohn wrote:wondering if the latest intel-microcode mitigates the issues with what I think Microsoft calls MDS
Code: Select all
cat /sys/devices/system/cpu/vulnerabilities/mds
https://www.mail-archive.com/source-cha ... 99141.html
deadbang
- ticojohn
- Posts: 1284
- Joined: 2009-08-29 18:10
- Location: Costa Rica
- Has thanked: 21 times
- Been thanked: 44 times
Re: Is hyper-threading still an issue
Yep, it's an issue. Hyper-threading was already enabled in the BIOS, I disabled it in grub using mitigations=auto,nosmt.Head_on_a_Stick wrote: Enable SMT from the firmware ("BIOS") setting and ask the kernel what it thinks:Code: Select all
cat /sys/devices/system/cpu/vulnerabilities/mds
Why did I do it that way? Because it is a pain in the backside to get into BIOS on my NUC. The NUC BIOS only supports a 1024x768 screen resolution and my non-smart TV does not support that resolution.
As always, thanks for your feedback.
I am not irrational, I'm just quantum probabilistic.