this post was submitted on 14 Aug 2023
88 points (98.9% liked)

Steam Deck

5713 readers
1 users here now

Universal community link
[email protected]

Rules

Order

Models

64GB eMMC LCD
256GB NVMe LCD
512GB NVMe LCD
512GB NVMe OLED
1TB NVMe OLED

Allowed languages

founded 3 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] [email protected] 12 points 1 year ago (2 children)

I want to see benchmarks on how this affects actual gameplay. That’ll be the real story.

[–] [email protected] 4 points 1 year ago (2 children)

From what I've seen the authors of the papers have listed the zenbleed mitigation impact as "statistically insignificant".

[–] [email protected] 4 points 1 year ago

Which was in stark contrast to Intel's "up to 50%" performance hit for the Downfall fix.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Which is clearly not correct. Take a look at eg. this benchmark; many workloads take a sizeable hit. Even plain 'ol glibc sin and cos take about 8% longer, and the most pathological hit was the MariaDB workload which took almost 200% longer. Looks like many tasks related to math or heavy-duty string processing will be at least 10-20% slower, but it's hard to say yet what this'll do to games. I'd expect CPU-heavy games to be affected

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)
[–] [email protected] 9 points 1 year ago

This is the best summary I could come up with:


Turns out the original code in the Linux kernel somehow missed the Steam Deck, so now it's being pulled in urgently to ensure it's also protected as per the patch:

Commit 522b1d69219d ("x86/cpu/amd: Add a Zenbleed fix") provided a fix for the Zen2 VZEROUPPER data corruption bug affecting a range of CPU models, but the AMD Custom APU 0405 found on SteamDeck was not listed, although it is clearly affected by the vulnerability.

Add this CPU variant to the Zenbleed erratum list, in order to unconditionally enable the fallback fix until a proper microcode update is available.

I'm sure some people will argue against it as these fixes can come with performance penalties, because the Steam Deck is primarily a gaming device.

But still, it has a full desktop mode it's not a traditional locked down console, you can install a browser and do basically anything with it - better to be safe than sorry.

If you're on desktop, as always it's a good idea to ensure you regularly check for updates to patch up issues like this.


I'm a bot and I'm open source!

[–] [email protected] 7 points 1 year ago (1 children)

Bit of a silly mitigation to have on the Deck, honestly. Hopefully there'll be a way to disable it; it's probably going to kick performance down by tens of percents, and I really don't need that on a gaming device where this particular attack is just incredibly unlikely and most likely wouldn't lead to jack shit anyhow.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

People have proven that the Steam Deck is pretty much just a daily desktop driver. People do all kinds of things on it. It also seems like its performance downgrade is insignificant.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

And I'm not one of those people so I'd like the option to not take the performance hit. Based on benchmarks I've seen it's definitely not going to be insignificant, but it's hard to say what the effect on games will be. See eg https://openbenchmarking.org/result/2308071-NE-2308068NE86, where math operations can be seen to take about 10% hits and some tasks go way above that. Not terrible but it's not going to be nothing either, which is why I'd like to be able to opt out

Edit: corrected the link