Intel Chips Have Memory Access Design Flaw and Fix Could Lead to Performance Drop

Apple still has a small market share (i.e. for mac). And more and more software is subscription based. Adobe and Microsoft would get on board, Apple’s own stuff would be fine, and most of the Indy developers would jump to ARM too (most stuff in the MAS, for sure). That would cover the vast majority of what most people use. Much of the rest would come over or would be replaced by new options.

--- Post Merged, Jan 3, 2018 ---

You can compile it yourself in Xcode. Here’s the source code:

func am_i_affected {
print(“yes”)
}

 

If there is such a performance drop (30%) following a fix, do you think manufacturers will have to compensate customers as the product is no longer ‘as described’ and may ‘not be fit for purpose’?

I have a mid-2012 15” Retina MacBook Pro.

 

I still have my vintage 2004 liquid-cooled PowerPC. It's time to re-activate that old monster!

 

That's quite the leap. Just because it isn't obvious to the masses that simply use these chips, doesn't mean it is a widely utilized design trap that is prone to catching designers. We have not heard of this happening to AMD, or the GPU designers or the ARM designers, etc. So far you merely have an unsubstantiated opinion based on nothing it seems.

 

It actually requires some extreme design laziness to speculatively execute instructions that will have results tossed due to memory isolation. This should have been caught, but probably the person who did the design worked on the same block for 10 years and no one else ever looked at it.

 

I was under the impression that EVERY Intel CPU made over the past 10 years was affected? At least according to the article on this site: "All modern computers with Intel chips from the last 10 years appear to be affected, including those running Windows, Linux, and macOS. "

So are you saying that only some CPU's are affected or all?

 

I'm saying they all are

 

It's Intel's crappy chips.

--- Post Merged, Jan 3, 2018 ---

AMD has publicly stated their chips do not and have not contained this flaw.

 

For all those worried about OSX... For what it is worth:

https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

"Finally, macOS has been patched to counter the chip design blunder since version 10.13.2, according to operating system kernel expert Alex Ionescu."

I haven't noticed any difference. Have you?

 

You are missing one HUGE thing. That's assuming those softwares were not compromised when you downloaded them. There have been a few cases of malicious software getting into developers' official distributions.

 

Or, see a bunch of stuff with: sysctl machdep

 

Ahh, okay. So what is the point of Intel releasing a tool for Windows (NOT macOS) to see if your chip is affected or not? Dumb. This is going to be one of the biggest class action lawsuits in U.S. history! Think of how many computers over the past 10 years with Intel CPU's are out there! Also, with Microsoft, you have to take in to account their Surface lineup since they all use Intel CPU's.

Would be really awesome if we all got new CPU's, I know I am dreaming on that one but damn, I am not taking a 30% hit in performance!

--- Post Merged, Jan 3, 2018 ---

Zero. Hmmm.

 

could be that there are (will shortly be) some fixed chips out there, or that you have an 11 year old chip and aren't sure how old it is.

 

How so?

 

Having to constantly flush the TLB can be a pretty massive performance hit for most types of workloads.

 

I have a 2015 MacBook Pro, with a Intel Broadwell chip in it. I will assume that it is affected!

Intel better do something really cool to help us out. I am not buying a new MacBook Pro to get a new Intel CPU which could still be affected! Intel should send me an upgraded version on my chip, based on socket size, and make sure it is not vulnerable to any attacks! Wishful thinking. 5-30% decrease is just unacceptable!

 

No, I have not noticed any performance impact.

 

Thirty effin percent?! What in the actual...?!
So the $3k 2017 MBP I bought a few months ago...30%?!?!
Apple will give me $900 back right?

 

Are you on macOS 10.13.2? Have you noticed any performance impact? The flaw has already been addressed in 10.13.2.

 

So far, after reading half of the replies, the first words of reason I read... thanks.

[sarcasm mode on]

- it's the end for Intel;
- everyone sees 30 percent hit, without much benchmarks, proofs or even patches at least on the Windows side;
- Apple will go ARM for sure...

[sarcasm mode off]

This site is named MacRumors for an obvious reason

Let's wait the official patches of Microsoft and Apple with real use benchmarks and then we'll see...

 

Nonsense. It's much easier to have righteous indignation based on perceptions rather than reality. Immediate overreactions based on incomplete information are the best.

 

You don't need to freak out about this, because you will probably never notice the difference. That comment was made as a worst case scenario with regards to Linux under assumptions that do not match real world use. It was just a long stream of system calls. Does that sound normal to you? If not, calm down.

Of course if the impact really was 30% on initial patch attempts, they would spend a lot more time working on ways to mitigate the problem.

 

Local Bus. LOL, I’ve been having flashbacks all day from this. It was my last PC.

 

Validated. Knew it would be soon. Didn’t know it’d be that soon.

 

Why would you look to Apple to compensate you for Intel’s screwup?