PC Perspective Podcast #482 – 1/04/18
Join us for discussion on Spectre, Meltdown, Cord Cutting, and more!
You can subscribe to us through iTunes and you can still access it directly through the RSS page HERE.
The URL for the podcast is: https://pcper.com/podcast – Share with your friends!
- iTunes – Subscribe to the podcast directly through the iTunes Store (audio only)
- Google Play – Subscribe to our audio podcast directly through Google Play!
- RSS – Subscribe through your regular RSS reader (audio only)
- MP3 – Direct download link to the MP3 file
Hosts: Ryan Shrout, Jermey Hellstrom, Josh Walrath, Allyn Malventano
Peanut Gallery: Ken Addison, Alex Lustenberg
Program length: 1:01:54
Podcast topics of discussion:
-
0:02:15 PCPer Mailbag #24 – 12/29/2017
-
Week in Review:
-
0:03:27 Just Picked Up: Google Wifi x4
-
-
News items of interest:
-
-
0:48:00 The top 20 games of 2017?
-
-
Picks of the Week:
-
0:53:25 Jeremy: MP Select Mini 3D Printer V2
-
0:55:00 Josh: A replacement cell phone battery? Unheard of!
-
0:56:10 Allyn: Retro Game Dev: C64 Edition
-
0:57:50 Alex: Broforce ($3.74 on steam winter sale)
-
Closing/outro
0:15:45 Meltdown and Spectre
0:15:45 Meltdown and Spectre Security Vulnerability Impacts Intel most, but AMD, Arm as well
Please retest Intel Optane, ok?
We’ve already done this, and
We've already done this, and the results are entirely uninteresting. More soon.
If there is no difference in
If there is no difference in Optane 4K random reads then I bet Intel took similar shortcut as with the cache.
AMD is currently not affected
AMD is currently not affected by Meltdown, and is only affected by Spectre.
The big concern for Intel based systems is that performance loss because of the speculative execution User-Space to Kernel-Space checking is not done before any speculative execution is allowed. So Intel now has to have Kernel-Space mapped via a higher overhead context switch from User-Space.
Intel cheaped out on the hardware checks needed just to get the better speculative utilization/IPC and now Intel has to pay the piper. AMD performs the check in advance of any speculative execution that may cross User-Space and Kernel-Space domains and that incurs a slight performance penalty but it prevents any Meltdown like occurrences on AMD’s CPU hardware. AMD will not allow speculative execution across User-Space and Kernel-Space code mapped into a page/address range so no need to incur the extra context switching overhead while Intel will have to incure the extra context switching overhead required by having the User-Space and the Kernel space mapped accross different address/page boundries.
Is it just me or are others
Is it just me or are others not seeing this episode show up in Pocket Casts?
I can confirm that it never
I can confirm that it never made the RSS feed.
Still waiting for it to show
Still waiting for it to show up.
It’s still not showing up in
It’s still not showing up in iTunes.
I just want to download the
I just want to download the audio version to my phone and its not showing up in my podcast app. How do we get their attention and let them know they didn’t publish it correctly? It doesn’t look like anyone at PC Per is keeping an eye on these comments!
Any ideas?