Podcast #482 - Spectre, Meltdown, Cord Cutting, and more!

Subject: General Tech | January 4, 2018 - 11:28 AM |
Tagged: Z370, Vega, spectre, msi, meltdown, Koolance, Kaby Lake G, google wifi, cord cutting, apple, Android, 400A-S, podcast

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: http://pcper.com/podcast - Share with your friends!

Hosts: Ryan Shrout, Jermey Hellstrom, Josh Walrath, Allyn Malventano

Peanut Gallery: Ken Addison, Alex Lustenberg

Program length: 1:01:54

Podcast topics of discussion:
  1. Week in Review:
  2. News items of interest:
  3. Picks of the Week:
  4. Closing/outro

Source:

January 4, 2018 | 05:43 PM - Posted by Power (not verified)

0:15:45 Meltdown and Spectre Security Vulnerability Impacts Intel most, but AMD, Arm as well

Please retest Intel Optane, ok?

January 4, 2018 | 11:21 PM - Posted by Ryan Shrout

We've already done this, and the results are entirely uninteresting. More soon.

January 5, 2018 | 04:26 AM - Posted by Power (not verified)

If there is no difference in Optane 4K random reads then I bet Intel took similar shortcut as with the cache.

January 5, 2018 | 01:48 AM - Posted by EnjoyTheExtraIntelOverhead (not verified)

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.

January 5, 2018 | 12:02 PM - Posted by Miles (not verified)

Is it just me or are others not seeing this episode show up in Pocket Casts?

January 6, 2018 | 01:27 PM - Posted by Listener #229 (not verified)

I can confirm that it never made the RSS feed.

January 6, 2018 | 02:12 PM - Posted by Blind Bubba (not verified)

Still waiting for it to show up.

January 7, 2018 | 03:44 PM - Posted by Anonokiller (not verified)

It’s still not showing up in iTunes.

January 9, 2018 | 02:50 PM - Posted by BuckTooth (not verified)

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?

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Lines and paragraphs break automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote><p><br>
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.