Yet another Intel speculation vulnerability: Side Channel L1 Terminal Fault

[HTC]

https://www.intel.com/content/www/us/en/architecture-and-technology/l1tf.html

It seems to affect mostly virtualized environments.

 

[qubit]

Oh not again.

 

[HTC]

Since AMD is also affected by some speculative execution security issues, i've no idea if this particular issue also affects them.

If anyone knows more about this, please leave your input and i'll update the OP accordingly.

 

[Caring1]

Hasn't this been found in vt-x already?

 

[R-T-B]

Hasn't this been found in vt-x already?

No. This appears new. And yes, largely affects VM hosts.

 

[Caring1]

No. This appears new. And yes, largely affects VM hosts.

Another good reason to turn it off in the BIOS unless needed.

 

[R-T-B]

Another good reason to turn it off in the BIOS unless needed.

I mean the fix has literally no performance impact to native code. You don't need to turn anything off.

You could read the linked article. It's all in there.

 

[Caring1]

I mean the fix has literally no performance impact to native code. You don't need to turn anything off.

You could read the linked article. It's all in there.

I have read it, and also have no need for virtualisation, so can turn it off

 

[R-T-B]

I have read it, and also have no need for virtualisation, so can turn it off

I mean, it appears the perfomance impacting code for even VMs is opt-in in the first place, so have at I guess? You literally can only do nothing for your use case messing in the bios.

 

[MrGenius]

So the latest Windows 10 Cumulative Update addresses this. Which I've installed and verified the mitigation for it is enabled. I don't want it enabled. So I need the PowerShell script used to disable it. Which I can't find anywhere. If anybody knows what it is, and/or where to find it, I'd be grateful if you could drop a link or do a copy-paste of it here for me.

Thanks!

 

[R-T-B]

So the latest Windows 10 Cumulative Update addresses this. Which I've installed and verified the mitigation for it is enabled. I don't want it enabled. So I need the PowerShell script used to disable it. Which I can't find anywhere. If anybody knows what it is, and/or where to find it, I'd be grateful if you could drop a link or do a copy-paste of it here for me.

Thanks!

There probably isn't a shutoff simply because there isn't a performance penalty for non guest OSes.

You guys seriously need to quit worrying. It isn't costing you an inkling of performance. Benches actaully went UP in one figure post mitigation.

 

[FordGT90Concept]

And they'll never stop finding more ways to exploit it until it is fixed (speculation eliminated?) in silicon.

 

[R-T-B]

speculation eliminated?

So you really expect them to make a superpowerful atom-gen1 style core?

 

[Final_Fighter]

There probably isn't a shutoff simply because there isn't a performance penalty for non guest OSes.

You guys seriously need to quit worrying. It isn't costing you an inkling of performance. Benches actaully went UP in one figure post mitigation.

can confirm this. at least in my case. i get an extra 10 points with my system in cpuz.

 

[FordGT90Concept]

So you really expect them to make a superpowerful atom-gen1 style core?

It'd fix the problem, permanently.

 

[biffzinker]

What could a quad core Atom do running at 5GHz?

 

[Vya Domus]

What could a quad core Atom do running at 5GHz?

Still not much.

 

[dorsetknob]

What could a quad core Atom do running at 5GHz?

Fusion

 

[Caring1]

What could a quad core Atom do running at 5GHz?

If all the cores can run concurrently, just over 1200% increase in performance.
Unless using Infinity Fabric then scaling wont be linear ..... k, enough trying to keep a straight face

 

[Bill_Bright]

Oh not again.

No. This appears new.

No, it is "not again" or "new". The article clearly says in the very first sentence that this is about "more details" about the previously announced problem.

 

[HTC]

There's another topic for this issue on the news section: i suggest this topic to be locked and the discussion be moved there instead.