The biggest performance hits are still upcoming for Intel

If you think KPTI performance impact is bad, wait until this Intel-specific Spectre fix lands in Linux:

lkml.org/lkml/2018/1/3/770

Basically every indirect call (one instruction) turns into a seven-instruction sequence (retpoline) that will, due to preventing speculation, result in massive slowdowns.

Unlike the KPTI patches, which only affect things on each system call, this happens on every indirect call and probably bloats the code considerably too.

These are the patches that prompted Linus' angry response, and it's understandable: it's not an exaggeration to say these patches will be the biggest Linux kernel performance regression in history.

Merging has been halted until the Intel devs add configuration flags to allow it to be disabled selectively (for example, for AMD CPUs).

Other urls found in this thread:

lkml.org/lkml/2018/1/3/797
lists.opensuse.org/opensuse-security-announce/2018-01/msg00004.html
marc.info/?l=openbsd-misc&m=118296441702631&w=2
bbs.archlinux.org/viewtopic.php?id=233233
bleepingcomputer.com/news/security/google-almost-all-cpus-since-1995-vulnerable-to-meltdown-and-spectre-flaws/
twitter.com/NSFWRedditGif

Oyy vey, delete that thread, goyim

unless you're running a database or doing highly specialized stuff like live music production, you won't notice the hit

>dont worry goy it doesnt matter

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
THIS CAN'T BE HAPPENIIIIIIIIIING
IT WAS NOT SUPPOSED TO BE LIKE THIS

>unless you're running a database or doing highly specialized stuff like live music production, you won't notice the hit
you're an idiot. all modern software has a built in database, and makes a shit ton of system calls. how do you think it gets i/o?

also, thanks to webdevs who can't program, every website is going to get extremely slow. if you think your browser dosen't have a built in database, or doesnt make a shit ton of syscalls, you are mistaken.

>spectre fix will only affect intel

None of this would happen if the kernel was just written in Rust.

>Merging has been halted until the Intel devs add configuration flags to allow it to be disabled selectively (for example, for AMD CPUs).

Those sneaky jews tried to make AMD pay for Intels fuckup?

wrong again, friendo.

it doesn't matter what code is being run on the machine, it's a hardware side channel attack. also using this i can run code on your machine to do whatever i want, like turn it off, or block Sup Forums. it's an intel hardware backdoor lol

This actually has nothing to do with syscalls, have you even read the OP? Indirect calls are everywhere in regular code.

Microsoft might as well patch Vista and XP which will kill the damned straggler's system performance.

This is an Intel-specific fix written by Intel engineers which uses Intel-specific architecture features, read the Andi Kleen emails.

My emulation already took a hit with the meltdown fix. I'm just gonna take my chances with this. No more slowdown.

What?

>tfw you didn't fall for the Intelaviv meme.

What's worse, according to:
lkml.org/lkml/2018/1/3/797

retpoline is a compile-time option with a patch set being pushed by Intel that does not allow a way to disable it dynamically for CPUs that aren't vulnerable.

Level that playing field, goy!

I'm never buying a Hebrew processor again

yes wasn't it clear by their sleazy inclusion of others but in general way without specifics just to make them look not that bad because you see it's not just them but in reality it is mostly them

>block Sup Forums
Imagine waves of hackers going about to millions of machines and blocking Sup Forums across the globe.

>already using an i5 3320M in my day to day laptop
>see these fucking threads everywhere
I haven't updated my OS for like 3 weeks now. What happens if I update Debian? Am I going to get bent over and fucked by this patch? AMD shills give me an honest answer, does this impact performance on AMD mobile chips? I'm due for a laptop upgrade and I'm thinking about dropping like $800 on an A-series ThinkPad. Please respond.

So... is this going to give insight into reverse engineering certain consoles architecture for emulation and piracy?

the fuck??

AMD isn't affected performance-wise by any of this so far. Maybe in the future an AMD-specific Spectre vulnerability is discovered and a performance-degrading patch is needed, but to date that hasn't happened and I bet Intel getting even more crippling fixes is more likely.

Sup Forums is here

How do I install homebrew on my 3ds?

>tfw no T/X/W thinkpads with AMD
>tfw no cheap servers with AMD
fucking jews with their almost monopoly position

Joke's on you, Intel doesn't have heavy R&D in Tel Aviv.

Thinkpads are botnet.

...

>list of affect intel CPUs

Intel® Core™ i3 processor (45nm and 32nm)
Intel® Core™ i5 processor (45nm and 32nm)
Intel® Core™ i7 processor (45nm and 32nm)
Intel® Core™ M processor family (45nm and 32nm)
2nd generation Intel® Core™ processors
3rd generation Intel® Core™ processors
4th generation Intel® Core™ processors
5th generation Intel® Core™ processors
6th generation Intel® Core™ processors
7th generation Intel® Core™ processors
8th generation Intel® Core™ processors
Intel® Core™ X-series Processor Family for Intel® X99 platforms
Intel® Core™ X-series Processor Family for Intel® X299 platforms
Intel® Xeon® processor 3400 series
Intel® Xeon® processor 3600 series
Intel® Xeon® processor 5500 series
Intel® Xeon® processor 5600 series
Intel® Xeon® processor 6500 series
Intel® Xeon® processor 7500 series
Intel® Xeon® Processor E3 Family
Intel® Xeon® Processor E3 v2 Family
Intel® Xeon® Processor E3 v3 Family
Intel® Xeon® Processor E3 v4 Family
Intel® Xeon® Processor E3 v5 Family
Intel® Xeon® Processor E3 v6 Family
Intel® Xeon® Processor E5 Family
Intel® Xeon® Processor E5 v2 Family
Intel® Xeon® Processor E5 v3 Family
Intel® Xeon® Processor E5 v4 Family
Intel® Xeon® Processor E7 Family
Intel® Xeon® Processor E7 v2 Family
Intel® Xeon® Processor E7 v3 Family
Intel® Xeon® Processor E7 v4 Family
Intel® Xeon® Processor Scalable Family
Intel® Xeon Phi™ Processor 3200, 5200, 7200 Series
Intel® Atom™ Processor C Series
Intel® Atom™ Processor E Series
Intel® Atom™ Processor A Series
Intel® Atom™ Processor x3 Series
Intel® Atom™ Processor Z Series
Intel® Celeron® Processor J Series
Intel® Celeron® Processor N Series
Intel® Pentium® Processor J Series
Intel® Pentium® Processor N Series

>reverse engineering certain consoles architecture
If you're thinking of recent consoles, they're all on AMD except Nintendo, so I don't think so. Meltdown affects Intel, Spectre would've affected AMD but AMD came right out and said no effect to 2 out of 3 of the variants. It's only the first spectre variant where if you're running a custom BIOS instead of default on certain FX machines that you're fucked unless it got patched.

I haven't seen this outside of opensuse, but there's an amd microcode patch that disables branch prediction on Zen to harden against spectre, so uh, rip Ryzen performance.

lists.opensuse.org/opensuse-security-announce/2018-01/msg00004.html

Shit is so bad that even the unrelenting shintel shills have toned down a bit.

>C2D not affected
Comfy af using my Q6600

Wow, that's almost all the letters of the alphabet!

>Basically every indirect call (one instruction) turns into a seven-instruction sequence (retpoline)

do not assume i know what I'm talking about, but this wouldn't need to be that bad (going for the "term" sequence), or are you explicitly saying that for every instruction there will be a 6 extra cycles demand?

>no C2Q on the list
never imagined I'd pull out my q9550 from the wreckage

Is this a seperate bug or the same bug?
What's Spectre 1 and Spectre 2?

>Intel® Celeron® Processor N Series
Processors that are already crawling going to be hit with a huge performance penalty. Oy vey!

How much performance does branch prediction really add?
What if Intel were to completely remove it instead of patching it in software?

I'm disheartened by the number of comments here who are taking the stance that Intel has idiot designers or that management doesn't care about security. This attack is very clever and unexpected, nobody could have predicted this. Intel still the dominant and most trusted industry player and will remain so in the future.

>those digits
>this shill

Right there mate: 2nd generation Intel® Core™ processors

YFW

>This attack
> This attack
it's a fucking design CHOICE

Did you test your system pre-after patch?
Mine had some degradation on win10 after patch, using Q9550.
That's Core ix-2xxx series

you've got it on point

someone give him an oscar

Fucking kill yourself you idiot shill

>tfw Intel Pentium G series

The fuck is this webm?
Any context?

>nobody couldve predicted this

i can think of someone

See the 5th row.
>2nd generation Intel Core
I.e Core2 duo.

Forgot image

a """girl" with a very very small penis trying to get a neovagina

Witnessed, mein neger!

That kid is a tranny. Google transexual dilatation.

Actually this has been know since 2007 but swept under the rug.

proof please?

Thank dog I bought a cheap g4560 in february and didn't spend in a more expensive CPU. Thanks ryzen hype I guess.

Not him, but Theo de Raadt (OpenBSD founder) has been warning about Intel CPU bugs for a long time: marc.info/?l=openbsd-misc&m=118296441702631&w=2

Shit really did hit the fan.

bad news for you

i tested on my trannyboot x200 and it's affected

so did i fuck by upgrading my t430 to a quad core few days ago?

Meant to reply to

>Allowing privileged reads in an unprivileged context
>Not completely idiotic

Emulation is CPU heavy. CPU usage gone up after patch.

I'm not sure what this would mean for performance, but Intel's modern pipeline is about ~20 steps long, so I'd assume that it means any conditionals are gonna cost that many extra cycles, if the OoOE can't fill in the gaps in the pipeline.

Someone with ryzen should go benchmark the opensuse with the microcode, if they want to test how much a lack of branch prediction will affect performance.

So was this vulnerability the reason why Intel has IPC numbers and will the fix lower IPC numbers

bbs.archlinux.org/viewtopic.php?id=233233
Only PassMark from all of the tested use cases took a drastic hit performance wise. The tests have been performed by Phoronix. Can anyone provide additional benchmarks?

...

No, you're going to need the extra power now.

He is wrong. They know that there was something they took 10 year to find it. You know. Because it was hard to find? Probably hard to put into practice too. Better stick to scamming old folk with fake paypal emails. less work.

What CPU, emulator and game?

That's for KPTI (Meltdown fix), this is different.

No
The worst is yet to come. There are more vulnerabilities screencap this post. Intel is still not telling how bad it really is.

It goes all the way done to Pentium Pro from 1995, everyone on Intel is fucked.

Are you sure Core 2 Duo isn't affected? I've got Thinkpads that use them.

If you don't use your donger much before The Surgery™, it can cause them to not have enough material to work with (since HRT shrinks the dingus).

>I'm disheartened
Of course you are, you fucking corporate shill, since it means fewer will be tricked to use your corrupt company's shitty hardware in the future.

so, it hasn't even started yet?

The fact that guy sold his shares tells me he expects more then just a dip. He expects a hard fall and he's bailing out. Otherwise, he'd ride it out.

How badly and what processor is in it? I've disconnected my Core 2 Duo machines until there's more information out.

Amerimutt at it again. lol

>Your system either does not have the appropriate patch, or it may not support the information class required.

Sigh, I wish Alex would stop shilling and add a check for a system running on AMD.

Of fucking course

Exactly this. This one is very serious.

wrong img

This looks extremely painful

Underrated.

For you

One can only hope

debian haven't patched yet so nothing

It's not on the list.

Is Core 2 Duo on the list under a slightly less obvious name or not, lads? And is that list complete?

The 3 variants includes both meltdown and specter-based attacks.
I say "*-based" attacks because the specter attack vector still exists on every single CPU with speculative execution.

It was predicted within the context of side channel attacks, that's why multiple researchers discovered Meltdown independently. It just took a while for the actual side channel techniques to catch up and create a practical exploit.

There is no list
bleepingcomputer.com/news/security/google-almost-all-cpus-since-1995-vulnerable-to-meltdown-and-spectre-flaws/
It's the feature on the CPU, it's been used since 1995. It's existed for 20 years.
Everything from Intel is impacted, except the Itanium processors.

It's a little more subtle than that because the privileged reads don't affect the architectural state but information is leaked via side-channel.
Of course it's still idiotic because side-channel attacks have been predicted for ages.

>At the time of writing, Google believes that "every Intel processor which implements out-of-order execution is potentially affected, which is effectively every processor since 1995 (except Intel Itanium and Intel Atom before 2013)" is affected by Meltdown.