News for hackers. Stuff that matters.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dsign on Wednesday January 03, 2018 @10:00AM (#16061463)
This is a clusterf/big deal. Beyond the security implications, it means that all companies paying for computing resources will have to pay roughly 30% more overnight on cloud expenses for the same amount of CPU, assuming that they can just scale up their infrastructure.

I know that bugs happen and that there was nothing intentional on this one, but at times like this is hard to held at bay the temptation of claiming for a class lawsuit against Intel....

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Wednesday January 03, 2018 @01:10PM (#16063384)
It's a good thing CPU is fairly compressible. Unless you meter it very carefully, you'll see the performance hit and it'll not impact you that much. Very few of my physical boxes are over 70% CPU utilization on a daily average.

It's, however, really bad if you sell CPU cycles for a living. You just lost between 5 and 30% of your capacity. If you have a large building, you just lost part of your parking lot to the Intel Kernel Page Problem building.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by devcpp on Wednesday January 03, 2018 @01:37PM (#16063676)
Problem is, most companies that need a lot of power only care about one thing - peak performance. And they tune it carefully in order to not overspend while guaranteeing minimal downtime. This means that they'll have to pretty much scale their infrastructure up by exactly 30%. That's a LOT for these big clients.

Honestly, I'd just make sure the server firewalls are super tight and not take in the future patches. At least for now.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ajross on Wednesday January 03, 2018 @01:47PM (#16063791)
Very very few highly tuned "peak performance" workloads are dominated by syscall overhead like the test that produced that 30% number was. It's best to hold off on the hyperbole.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dijit on Wednesday January 03, 2018 @04:18PM (#16065255)
I have a power dependent workload that scales horizontally and is currently already dominated by the cost of system calls. This will effectively, directly cause me to buy 30% more compute on a huge infrastructure. (2,000~physical machines. Quite beefy dual socket machines with a lot of memory)

I know I’m not alone.

Then again. Think of microservices, Kubernetes for instance; Network requests are system calls.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Wednesday January 03, 2018 @04:41PM (#16065473)
If your workload has no code that's untrusted, you can safely skip this patch or disable it on boot. If not, at 2000+ physical machines, it may be worth to move some of that into kernel modules that would collapse a couple syscalls into a single higher level one.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ufo on Wednesday January 03, 2018 @09:20PM (#16067460)
The VM host will still have the patch applied, won't it?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Thursday January 04, 2018 @05:26AM (#16069229)
Yes, but if it's your metal, you don't need to.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dijit on Thursday January 04, 2018 @04:11AM (#16068946)
Good idea. But it’s a windows executable and depends quite heavily on windows specifics.

(In my case anyway)

30% overhead might be inscentive to revisit the assumption we can’t rewrite it for Linux.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Thursday January 04, 2018 @05:29AM (#16069240)
You still can move some functionality to a device driver or something else that runs in the NT kernel space.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rogerthis on Wednesday January 03, 2018 @08:06PM (#16067095)
But then you have to release the module as GPL, no?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by lmm on Thursday January 04, 2018 @07:01AM (#16069685)
Only if you want to do something that would otherwise be a violation of copyright - e.g. distribute the module to other people (assuming it's sufficiently entangled with linux to be a derivative work therof). The GPL only licenses you to do things that you otherwise couldn't do, it doesn't restrict you from doing things that were never a violation of copyright (e.g. privately modifying your own things).
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by KingMachiavelli on Wednesday January 03, 2018 @09:44PM (#16067575)
No kernel modules can be closed source; GPU drivers are a common example of a closed source kernel module.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by maxander on Wednesday January 03, 2018 @05:43PM (#16066082)
Will you be buying Intel-based machines? Or will you be running a hybrid-architecture cluster now?

I don’t know very much about computing on that scale, but I wonder if all the people selling off Intel stock are thinking this story through.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by lev99 on Wednesday January 03, 2018 @06:39PM (#16066585)
AMD server CPUs currently outperform Intel on some multi-threaded benchmarks. This usually isn't a problem for people buying for peak-performance because you can always buy more CPUs to increase parallel programming speeds, but it's harder to make single threads faster.

It's possible that the patches applied to fix this bug will cause some single-threaded benchmarks to change from Intel being the fastest to AMD being the fastest.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by myrandomcomment on Wednesday January 03, 2018 @09:54PM (#16067642)
So for what it is worth my company has all Intel kit. We run servers that run docker. In each docker container we do build / test for our product. That is all we use them for. 1RU with 2 blades, each blade is dual socket, 72 total cores, 512GB RAM. We will not apply this patch as none of this is public facing and we do not want the hit to build / test throughput. The one big thing that this has done is we were looking at AMD for new servers and that has now become a higher priority on the to do list. Given our environment we care about the number of containers we can run, period.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dijit on Thursday January 04, 2018 @04:13AM (#16068954)
It is overwhelmingly likely that we’ll buy more intel. Power/Watt has always been superior and AMD has to prove itself over time before we’d buy it.

Not trying to kill expectations. This decision isn’t mine alone. You know the old saying “nobody got fired for buying Cisco” that applies to Intel too.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bpchaps on Wednesday January 03, 2018 @03:02PM (#16064515)
No, but lots of workloads are built with latency in mind. For APIs that talk to each other in long serial chains, don't be surprised if request responses take significantly longer in many, many workflows.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by brazzledazzle on Wednesday January 03, 2018 @03:01PM (#16064500)
I wouldn’t isolate your concern to firewalls and bad actors that break in over SSH. If they manage to find a vulnerability in your app that allows remote code execution this could help them make that problem much worse. Also VM/container escapes are a big problem if you use a cloud provider.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by redcalx on Wednesday January 03, 2018 @03:20PM (#16064680)
> I'd just make sure the server firewalls are super tight and not take in the future patches. At least for now.

Good security is about layers. No one layer can be assumed to be watertight, but with enough layers you hopefully get to a good place.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by viraptor on Wednesday January 03, 2018 @02:19PM (#16064123)
If they really care about peak performance, I don't believe the PTI patch will affect them. If you can change your system in a way that the power-hungry part does not work on untrusted data, you can not with "nopti" and ignore it. Systems which both need lots of maxed-out CPUs and traffic directly from wild internet are pretty rare. They're unlikely to run on a virtualised systems either.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by btilly on Wednesday January 03, 2018 @02:39PM (#16064313)
Systems which both need lots of maxed-out CPUs and traffic directly from wild internet are pretty rare.

That's a good description of basically every cloud environment out there, from AWS on down.

In other words they are extremely common.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Wednesday January 03, 2018 @03:02PM (#16064514)
There are many ways to tune such workloads and I suspect our software will get better as a result.

We'll start to get conscious about the number of syscalls we use on each operation, start using large buffers, start buffering stuff user-side...

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by viraptor on Wednesday January 03, 2018 @03:40PM (#16064875)
The CPUs in cloud environments are not maxed out in general. There will be some area like batch processing and compute-specific VMs. For other cases, there's quite a bit of overcommitting of resources. And that's before you start doing scheduling that mixed workloads on a physical host for better utilisation. Source: worked on a public cloud environment.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by btilly on Wednesday January 03, 2018 @05:17PM (#16065816)
I agree with you on most VMs. But once you schedule mixed workloads, you want each host to be balanced so that all of its capacity is utilized evenly. Which means that if CPU use increases across the fleet, you will want new hardware with more CPU.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Thursday January 04, 2018 @05:31AM (#16069246)
Either that, or you'll have to put up with some processes taking longer.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by steve_gh on Wednesday January 03, 2018 @11:12PM (#16067983)
About 10 years ago I was mentored by a guy who was an utter wizard at queuing theory, and who bugfixed a whole bunch of nasty issues in cellular telecoms hardware through his understanding of how queuing theory impacted code execution.

TL:DR - queue behaviour gets nonlinear as you approach the theoretical max load. If you are running your processors at a high load, even a small change in code throughput makes a huge difference to real world behaviour.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by azeirah on Thursday January 04, 2018 @06:37PM (#16075131)
I believe I saw a strangeloop talk about this specific issue in Clojure. The talk giver was talking about channels, not queues though.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by gleenn on Sunday January 07, 2018 @03:59AM (#16089970)
Do you have a link?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by topspin on Wednesday January 03, 2018 @01:59PM (#16063932)
Hmm. Since everyone that sells (Intel) CPU cycles for a living suffers the same loss of supply this boils down to pricing; the same demand chasing fewer cycles will drive up prices and the market will adapt.

30% is a big hit. I'm wondering if that isn't a bit exaggerated, or perhaps the consequence of a poorly optimized workarounds that will rapidly improve. I recall seeing figures on the order of 3% only a few days ago.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by btilly on Wednesday January 03, 2018 @02:41PM (#16064330)
30% is a worst case for a workload optimized to hit the performance bug as hard as possible.

How big it will be for your workload is a function of what your workload is. Benchmark if it is important to you.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by earenndil on Thursday January 04, 2018 @12:48AM (#16068333)
50%, rather, is the worst case scenario. 30% is a bad case scenario, and 5% best-case scenario. Which is still a lot for large cloud providers like amazon, google, microsoft.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dx034 on Thursday January 04, 2018 @07:13AM (#16069751)
Any public information on how someone like Google or Facebook handle this? Do they have enough spare capacity to patch or will they need to build further capacity first? I could imagine 10% of Google's capacity (internal services, not Google Cloud) is at least a large datacentre.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by earenndil on Friday January 05, 2018 @08:29PM (#16083272)
I know someone who works for amazon and he said that they didn't need to do anything or buy any more servers.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ktta on Wednesday January 03, 2018 @01:59PM (#16063925)
>It's, however, really bad if you sell CPU cycles for a living.

Who really sells CPU cycles? Cloud providers sell instances priced per core. So the real hit is by the customers since they have to shell out for more instances for the same amount of computing power.

The hit I see is by providers of 'serverless' computing, since they charge per request and have their margins reduced.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by zedpm on Wednesday January 03, 2018 @02:43PM (#16064359)
> The hit I see is by providers of 'serverless' computing, since they charge per request and have their margins reduced.

AWS, Azure, and GCP all bill serverless with a combination of per-request fees and compute (GB-seconds), so I'd expect the entire hit to be passed on to the user since this will cause increased compute time for each request. N requests that used to average 300ms each will now be N requests that average, say, 400ms, so the per-request billing remains the same and the compute billing will increase by approximately 30%.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ktta on Wednesday January 03, 2018 @05:39PM (#16066049)
I don't understand what exactly you're saying. All of those services have serverless services, but they also have server based instances which abstract compute to amount of cores and RAM rather than CPU cycles. And most use is out of the services which aren't serverless.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by TotallyHuman on Thursday January 04, 2018 @03:13PM (#16073654)
Then it's because you don't know how modern cloud works.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ktta on Thursday January 04, 2018 @05:23PM (#16074659)
I now see that my misunderstanding was about who exactly the users were and who the provider was. My opinion of provider was only GCE, AWS, etc. while the commenter I believe when talking about providers included users of those services (who again were providers of serverless services).
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by user5994461 on Thursday January 04, 2018 @12:20AM (#16068240)
A lot of companies do, including many ycombinator startups. Think of anything that's analytics, data science, data warehouse or advertising related. The costs to run their service just took a hit.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Houshalter on Wednesday January 03, 2018 @02:11PM (#16064028)
Their competitors are also affected.

Also a 30% decrease is also equivalent to setting Moore's law back 7 months. A 5% loss is only setting it back 1 month. I know that's a bit of a naive calculation. But the point is computing power has long operated in an exponential domain. So big differences in absolute numbers aren't necessarily a big deal.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by seccess on Wednesday January 03, 2018 @02:17PM (#16064097)
According to this patch comment, AMD x86 chips are not affected: https://lkml.org/lkml/2017/12/27/2
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mulmen on Wednesday January 03, 2018 @02:56PM (#16064469)
Sure but who is using AMD chips in place of Intel server chips? If company A competes in the widget market against company B and they both built their server infrastructure on Intel then neither company gained an advantage due to a performance degradation in Intel hardware.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by geezerjay on Friday January 05, 2018 @02:09PM (#16080781)
> Sure but who is using AMD chips in place of Intel server chips?

Well... Everyone who bought AMD. Some people managed to see beyond the hype and go for the optoon that made sense.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mulmen on Friday January 05, 2018 @04:01PM (#16081597)
The overwhelming majority of the cloud runs on Intel. Saying AMD is slightly better off doesn't really help if my systems are built on Intel. This is the case for most people.

What hype are you referring to? Are you suggesting the people who bought AMD knew this was a problem for Intel?

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by pi-rat on Wednesday January 03, 2018 @03:23PM (#16064702)
Azure got some AMD EPYC.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by JohnJamesRambo on Wednesday January 03, 2018 @03:24PM (#16064717)
>Sure but who is using AMD chips in place of Intel server chips?

Maybe a lot more now?

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by jjwiseman on Wednesday January 03, 2018 @03:35PM (#16064823)
CPU speed hasn't followed Moore's law since 2003ish. (Number of transistors is still following Moore's law, but that doesn't necessarily directly help you when your program is suddenly 3-30% slower.)
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Houshalter on Wednesday January 03, 2018 @03:55PM (#16065033)
A CPU from 2017 is going to run your programs a hell of a lot faster than one from 2003. Even if they technically have the same clock speed. Look at benchmarks for instance: https://www.cpubenchmark.net/high_end_cpus.html
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by RobAtticus on Wednesday January 03, 2018 @04:20PM (#16065285)
The claim wasn't "CPUs in 2017 are not faster than CPUs in 2003" or even "CPUs in 2017 are not much faster than CPUs in 2003"; the claim was that they haven't followed Moore's law since 2003, so applying it to CPU speed nowadays is inaccurate. Of course CPUs are faster now than they were 14 years ago, just not as fast as the case where Moore's law still applied to CPU speed.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by lttlrck on Wednesday January 03, 2018 @05:33PM (#16065976)
Moore’s Law doesn’t describe CPU clock speed increases.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by slededit on Thursday January 04, 2018 @04:35AM (#16069042)
Dennard scaling however did deal with clock speed (indirectly via power). It has failed since about 2005.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bunderbunder on Wednesday January 03, 2018 @04:09PM (#16065172)
I don't think you can reliably phrase this in terms of Moore's law. Moore's law mostly concerns raw FLOPs. It's less useful for predicting hardware performance for operations that are governed by limitations like I/O and memory latency. And this slowdown, if I understand it correctly, is largely driven by memory latency.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by adrianratnapala on Wednesday January 03, 2018 @09:59PM (#16067667)
One of the rationales for cloud computing is it saves money by cracking up utilisation. Providers observe how much users "really" use and then provisioning that much.

True, sometimes you will leave boxes at low utilisation for various reasons, e.g. to deal with traffic spikes. But those reasons have not gone away. So now instead of heaving a predictable increase in CPU cost, you have an unpredictable increase in performance snafus.

The only good news is that the real performance hit will be less than 30% on many workloads. Especially once the providers start juggling and optimising.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bogomipz on Wednesday January 03, 2018 @01:40PM (#16063705)
>"It's a good thing CPU is fairly compressible."

What do you mean by "compressible"?

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by theoh on Wednesday January 03, 2018 @01:47PM (#16063798)
Presumably, for a certain important class of application, CPU is not used "densely", i.e. continually. Instead it's used intermittently, like a gas rather than a solid... Hence compressibility. Such applications are far from being CPU-bound, in other words.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bogomipz on Wednesday January 03, 2018 @01:52PM (#16063848)
So a cloud provider would be an example. Compressible similar to a sparse file I guess as well. Thanks this makes sense.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by laythea on Wednesday January 03, 2018 @02:19PM (#16064115)
I think it was meant that a normal application does not utilise the CPU all the time, which can be seen by looking at the task manager CPU usage % = X. Any extra processing needed to fix this bug will have to come out of the remaining 100-X%. This is OK as long as you have enough spare %, and can afford the extra power usage for that processing.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bogomipz on Wednesday January 03, 2018 @02:48PM (#16064400)
That makes sense, thanks. This is a big deal.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Wednesday January 03, 2018 @03:27PM (#16064748)
Virtualization is one popular way to drive up CPU utilization. The more diverse workloads run on a given server, the more even the CPU usage tends to get. This way, if you have 100 workloads that peak at 100% but average at 1%, your CPU usage will tend to be smooth at 100%, any overallocation will smooth out over time (a job that would take 1 second may take up to 10).
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by asplake on Wednesday January 03, 2018 @01:33PM (#16063629)
No vendor can afford to do it at a loss for long. One way or another the customer will end up paying
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by exabrial on Wednesday January 03, 2018 @01:43PM (#16063746)
There's also latency though :/ it seems that programs that make a lot of syscalls will be affected more than programs that are doing in-process calculations
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbanffy on Wednesday January 03, 2018 @03:30PM (#16064773)
We'll start being more syscall conscious when we write our programs. We'll batch more at the user mode side and try to use less syscalls to do the job.

Kernel ABIs will eventually reflect that and crop up higher level expensive calls that replace groups of currently cheap syscalls (that will become expensive after the fix).

And Intel will profit handsomely from next generation CPUs that'll get an instant up-to-30% performance boost for fixing this bug.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by pkaye on Wednesday January 03, 2018 @05:00PM (#16065666)
What about all the kernel interrupts due to network and storage traffic?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by exabrial on Wednesday January 03, 2018 @05:27PM (#16065913)
Maybe the scheduler could dedicate a core to interrupts and software that has small quanta and page tables? Can't really think of a code solution that doesn't sound stupid when I type it.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by 0xTJ on Wednesday January 03, 2018 @08:39PM (#16067263)
Another consideration is power usage in data centers. Server power usage is annoyingly complex, and once you get above 70% utilization power usage may go up considerably.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by oliwarner on Wednesday January 03, 2018 @10:56AM (#16062006)
As a billion other people have already said, that all depends on their workloads. This isn't a 30% clockspeed deduction.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by prudhvis on Wednesday January 03, 2018 @11:42AM (#16062489)
As i understand the problem, this isn't about clockspeed reduction, now it is the software's responsibility to check if the page is a kernel page/user page. So, the impact is significant. So, every time either pages are touched/accessed this check needs to be triggered, which causes it to be much slower.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by DSMan195276 on Wednesday January 03, 2018 @12:40PM (#16063034)
> So, every time either pages are touched/accessed this check needs to be triggered, which causes it to be much slower.

Not to be mean, but that's not what is being changed.

You're right on the bug - userlevel code can now read any memory regardless of privilege level. However the fix isn't to manually check the privileges on each access - that would be extremely slow and wouldn't actually fix the problem.

The fix is to unmap the kernel entirely when userspace code is running. Because the kernel will no longer be in the page-table, the userspace code can no longer read it. The side-effect of this is that the page-table now needs to be switched every-time you enter the kernel, which also flushes the TLB and means that there will be a lot more TLB misses when executing code, which slows things down a lot.

So, to be clear, it is not accessing pages that is being slowed down, it is the switch from the kernelspace to the userspace.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Cyph0n on Wednesday January 03, 2018 @01:02PM (#16063299)
But doesn't the CPU enter kernelspace every time a syscall takes place? So based on what you've described, every time a syscall returns control back to userspace, the TLB will be flushed, which means slower page access times in general.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by DSMan195276 on Wednesday January 03, 2018 @02:25PM (#16064171)
The distinction I was trying to make was the above commenters thinking that the kernel is now checking page permissions instead of the CPU doing it - IE. Doing privileged checks in software. That's not what's happening, the kernel is just unmapping itself when usercode is run so the kernel can't be seen at all. Then the privileged checks (which are now broken) don't matter because there is no kernel memory to read.

All your points are right though. Page access times will in general be slower because of all the extra TLB flushes, leading to more TLB misses when accessing memory.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cortesoft on Wednesday January 03, 2018 @12:45PM (#16063081)
Right, but how often that happens is workload dependent. Basically, how often is your code making syscalls.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Cyph0n on Wednesday January 03, 2018 @01:06PM (#16063331)
But don't all FS accesses (e.g., write to socket, read from DB) require a syscall? In that case, basically all web applications would be affected.

Or am I completely off the mark?

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cortesoft on Wednesday January 03, 2018 @01:21PM (#16063492)
No, you are correct. Really, every application will be affected, they all make some syscalls. How much will vary, though.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by lmm on Thursday January 04, 2018 @07:04AM (#16069704)
At least one syscall happens at some point, but performance-tuned systems already use "bulk" syscalls where a single syscall can send megabytes of data, check thousands of sockets, or map a whole file into your address space to access as if it were memory.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by vidoc on Wednesday January 03, 2018 @12:54PM (#16063195)
> how often is your code making syscalls.

And how often the kernel services interrupts.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by moonbug22 on Wednesday January 03, 2018 @02:34PM (#16064260)
You don't understand the problem.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cornholio on Wednesday January 03, 2018 @11:33AM (#16062382)
> claiming for a class lawsuit against Intel

If people who received written assurance from Intel that their hardware is 100% bug free can form a legal class, sure. I highly doubt there is even a single one such customer.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by golfer on Wednesday January 03, 2018 @11:36AM (#16062418)
Anyone can sue anyone else at any time. If you think Intel isn't going to be sued for this, you're wrong.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cornholio on Wednesday January 03, 2018 @11:48AM (#16062566)
It depends on how they handle user compensation. Going by the FDIV precedent, they should typically replace all defective products for free, and they will be in the clear.

What I meant was that the presence of the bug itself is not a valid cause, for example you can't claim that due to the error you lost 1 trillion dollars via a software hack - even if it's true. If Intel can prove they acted ethically when disclosing the bug and that they replaced / compensated users up to the value of the CPU, they are in the clear.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by macintux on Wednesday January 03, 2018 @12:48PM (#16063124)
I read that this bug goes back several years; "replacing all defective products for free" could be a massive expense, and assuming it includes current chips, there's also some lag time and engineering effort to get to the point where they could start doing so.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by throwaway613834 on Wednesday January 03, 2018 @01:20PM (#16063487)
How do they replace defective products? Or more specifically how do you get your laptop CPU replaced if Intel offers a replacement for free?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cornholio on Wednesday January 03, 2018 @01:40PM (#16063709)
Presumably, by visiting an agreed service center in your western, sue-happy country, or sending the computer to the nearest one on your expense in the rest of the world. If the CPU is not replaceable or no longer in service, you would get a voucher for the lost value of the CPU/computer that is now 30% slower. Something like 10-20$ for anything older than 3 years, so most people won't bother. If Apple can do it, surely Intel will manage, but it will cost them in the billion order of magnitude, a non-negligible fraction of their yearly profit.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by golfer on Wednesday January 03, 2018 @11:58AM (#16062656)
Good call. Will be fascinating to see how this plays out!
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ianai on Wednesday January 03, 2018 @11:42AM (#16062495)
They need some legal standing or the case can be dismissed out of hand. It may very well be a question of who has the better legal team.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by AnimalMuppet on Wednesday January 03, 2018 @01:56PM (#16063902)
> They need some legal standing or the case can be dismissed out of hand.

Yes and no. Yes, Intel would get a chance to claim that the case should be dismissed out of hand. To do that, they have to prove that, even assuming all the claimed facts are true, the people suing still don't have a valid case. That's a high bar. It can be reached - there's a reason that preliminary summary judgment is a thing in court cases - but it takes a really flawed case to be dismissed in this way.

How flawed? SCO v. IBM was not completely dismissed on preliminary summary judgment, and that was the most flawed case I've ever seen.

> It may very well be a question of who has the better legal team.

Well, Intel can afford to hire the best. A huge class-action suit can sometimes attract the best to the other side as well, though. (There's not just one "best", so there's enough for both sides of the same court case.)

IANAL, but it looks to me like there's at least the potential for a valid court case. CPUs are (approximately) priced according to their ability to handle workloads; if they can't provide the advertised performance, they didn't deserve the price they sold for.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by user5994461 on Thursday January 04, 2018 @12:32AM (#16068280)
What is bug free? CPUs work just fine. There is no bug.

The question is did anyone receive performance assurance from Intel? Probably not.

Some cloud providers or compute grids just lost a lot. Maybe they will find an angle to claim compensation.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ashelmire on Wednesday January 03, 2018 @10:39AM (#16061842)
From what I've read, this slowdown only affects syscalls, which, since they aren't usually a huge percentage of processing in the first place, should not have such an effect. You're more likely looking at a few percent at most, which is not going to be enough to make AMD outperform Intel. Let's stop the fear mongering and wait for actual metrics.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by vardump on Wednesday January 03, 2018 @10:43AM (#16061878)
> From what I've read, this slowdown only affects syscalls

Incorrect. It also affects interrupts and (page) faults.

Any usermode to kernel and back transition.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by api on Wednesday January 03, 2018 @10:52AM (#16061963)
So this is evil for virtualization hosting, which is the major enterprise application for Intel chips.

Hosting on bare metal will become more attractive. Too bad you can't long OVH and Hetzner.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by chrisper on Wednesday January 03, 2018 @11:31AM (#16062360)
>Too bad you can't long OVH and Hetzner.

What does that even mean?

Also Hetzner just introduced some AMD Epyc server.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by golfer on Wednesday January 03, 2018 @11:37AM (#16062436)
"Long" as a verb means to purchase their stock.

As opposed to "shorting" a stock, which means making a bet that it will go down in value.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by chrisper on Wednesday January 03, 2018 @11:46AM (#16062544)
Ah that makes sense. Thanks!
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbjorklin on Wednesday January 03, 2018 @11:40AM (#16062468)
For some reason I can’t reply to ‘chrisper’ but I think ‘api’ is referring to going long in the stock market.

https://www.investopedia.com/terms/l/long.asp

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Splines on Wednesday January 03, 2018 @12:13PM (#16062780)
> For some reason I can’t reply to ‘chrisper’

HN doesn't let you do this to new comments to avoid back-and-forth commenting that is typical in flamewars.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by sli on Wednesday January 03, 2018 @12:57PM (#16063242)
Coming up on 9 years here and I'm still finding out new things about how this site works. I've been wondering recently why some comments aren't replyable.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by jfoutz on Wednesday January 03, 2018 @01:27PM (#16063564)
I think there is a time delay. Wait a few minutes or hours and you can reply. That cooling off period has helped me really think through my replies.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by AnimalMuppet on Wednesday January 03, 2018 @01:59PM (#16063928)
They become replyable after some amount of time. The amount of time varies based on how active the thread is and/or how deeply nested the comment is.

You can reply anyway, but you have to click on the timestamp ("X minutes ago") to do it.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by pbhjpbhj on Wednesday January 03, 2018 @01:20PM (#16063485)
Usually you can click on the <posting time> and go to a page that displays only that comment, which has a reply box even when there's no reply option on the main page.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bandrami on Wednesday January 03, 2018 @02:08PM (#16064006)
That 100Hz timer tunable just got a lot more attractive...
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dx034 on Thursday January 04, 2018 @07:17AM (#16069773)
Does that mean that you can get an instance on AWS and slowdown the underlying server for all others by forcing a lot of syscalls? Or how is performance distributed between tenants?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by DocSavage on Wednesday January 03, 2018 @10:48AM (#16061926)
Prelim benchmarks show a significant impact (~20%) on Postgresql benchmarks.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by paulmd on Wednesday January 03, 2018 @01:01PM (#16063287)
20% when running SELECT 1; over a loopback network interface, not in real-world workloads.

The other benchmark that has generated some consternation is running 'du' on a nonstop loop.

Both of these situations are pathological cases and don't reflect real-world performance. My guess is a 5-10% performance hit on general workloads. Still significant, but nowhere near as bad as some of the numbers that are getting thrown around.

And, databases are the worst case scenario, most real-world applications are showing 1% performance impact or less.

https://www.computerbase.de/2018-01/intel-cpu-pti-sicherheit...

https://www.hardwareluxx.de/index.php/news/hardware/prozesso...

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by eberkund on Wednesday January 03, 2018 @01:38PM (#16063689)
It's not really a worst case scenario when you consider where the majority of Intel's revenue comes from: selling their high margin server chips for use in data centers, a significant portion of which are running some kind of database.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ricardobeat on Wednesday January 03, 2018 @01:10PM (#16063389)
Why should we trust your guesses over numbers being thrown around?

Your last link is all gaming benchmarks, which as the article mentions are not affected much.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by sllabres on Wednesday January 03, 2018 @02:03PM (#16063958)
Another quick postgres estimate [1] with lower impact and a a reply from Linus Torvalds that this values are in the range what they are expecting from the patch. "... Something around 5% performance impact of the isolation is what people are looking at. ..." [2]

[1] http://lkml.iu.edu/hypermail/linux/kernel/1801.0/01274.html [2] http://lkml.iu.edu/hypermail/linux/kernel/1801.0/01299.html

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mschaef on Wednesday January 03, 2018 @10:42AM (#16061875)
> syscalls, which, since they aren't usually a huge percentage of processing in the first place... Let's stop the fear mongering

Agreed!

(We should probably also stop overgeneralizing about the nature of computational workloads.)

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by hinkley on Wednesday January 03, 2018 @12:29PM (#16062929)
Software development workflows have some of the worst syscall profiles out there. This is going to hit most of us where we live.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by wyager on Wednesday January 03, 2018 @10:20AM (#16061647)
> I know that bugs happen

This isn’t an excuse for Intel consistently having terrible verification practices and shipping horrendous hardware bugs. From 2015: https://danluu.com/cpu-bugs/ There have been more since then.

I’ve talked to multiple people who work in intel’s testing division and think “verification” means “unit tests”. The complexity of their CPUs has far surpassed what they know how to manage.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by zouhair on Wednesday January 03, 2018 @10:35AM (#16061790)
This is typically what happens when you go for a long time without real competition. You get way too comfortable and bad habits start to pile up.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by spdy on Wednesday January 03, 2018 @10:39AM (#16061834)
Isn't why this problem even exits the exact opposite? Intel was losing on the mobile market and changed internal testing to iterate faster by cutting corners.

Found a quote:

"We need to move faster. Validation at Intel is taking much longer than it does for our competition. We need to do whatever we can to reduce those times… we can’t live forever in the shadow of the early 90’s FDIV bug, we need to move on. Our competition is moving much faster than we are".

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by kabdib on Wednesday January 03, 2018 @12:43PM (#16063068)
Man, you should see the errata for some ARM-based SOCs. It's amazing that they work at all.

Vendor, in conversation: "We're pretty sure we can make the next version do cache coherency correctly."

Me (paraphrased): "Don't let the door hit you in the ass on the way out."

Management chain chooses them anyway, I spend the next year chasing down cache-related bugs. Fun.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by djsumdog on Wednesday January 03, 2018 @01:42PM (#16063734)
ARM is such a shitstorm. At least the PC with UEFI is a standard. With every ARM device, you have to have a specialized kernel rom just for that device. There have been efforts made on things like PostmarketOS, but still in general, ARM isn't an architecture. It's random pins soldered to an SoC to make a single use pile of shit.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by madez on Wednesday January 03, 2018 @03:00PM (#16064494)
Why is it an issue to need a different kernel image for each device? I don't see a problem as long as there is a simple mechanism to specify your device to generate the right image. It's already like that with coreboot/libreboot/librecore, and it worked just fine for me.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by kabdib on Wednesday January 03, 2018 @11:18PM (#16068000)
Imagine that you are the person leading the team that's making an embedded system on an ARM SOC. It's not Linux, so you have your own boot code, drivers and so forth. It's not just a matter of "welp, get another kernel image." You're doing everything from the bare metal on up.

(I should remark that there are good reasons for this effort. Such as: It boots in under 500ms, it's crazy efficient, doesn't use much RAM, and your company won't let you use anything with a GPL license for reasons that the lawyers are adamant about).

So now you get to find all the places where the vendor documentation, sample code and so forth is wrong, or missing entirely, or telling the truth but about a different SOC. You find the race conditions, the timing problems, the magic tuning parameters that make things like the memory controller and the USB system actually work, the places where the cache system doesn't play well with various DMA controllers, the DMA engines that run wild and stomp memory at random, the I2C interfaces that randomly freeze or corrupt data . . . I could go on.

It's fun, but nothing you learn is very transferrable (with the possible exception of mistrust of people at big silicon houses who slap together SOCs).

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by madez on Thursday January 04, 2018 @12:04AM (#16068176)
The responsibility to document the quirks and necessary workarounds lie with the manufacturer of the hardware. If the manufacturer doesn't provide the necessary documentation, then that's exactly that: insufficient documentation to use the device.

There are hardware manufacturers that are better than others at being open and providing documentation. My minimal level of required support and documentation right now is mainline linux support.

Can you document your work publicly, or is there something I can read about it? I'm very interested in alternative kernels beside Linux.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by kabdib on Sunday January 07, 2018 @02:22PM (#16092154)
> The responsibility to document the quirks and necessary workarounds lie with the manufacturer of the hardware.

When you buy an SOC, the /contract/ you have with the chip company determines the extent and depth of their responsibility. On the other hand, they do want to sell chips to you, hopefully lots of them, so it's not like they're going to make life difficult.

Some vendors are great at support. They ship you errata without you needing to ask, they are good at fielding questions, they have good quality sample code.

Other vendors will put even large customers on a tier-1 support by default, where your engineers have to deal with crappy filtering and answer inane questions over a period of days before getting any technical engagement. Issues can drag on for months. Sometimes you need to get VPs involved, on both sides, before you can get answers.

The real fun is when you use a vendor that is actively hiding chip bugs and won't admit to issues, even when you have excellent data that exposes them. For bonus points, there are vendors that will rev chips (fixing bugs) without revving chip version identifiers: Half of the chips you have will work, half won't, and you can't tell which are which without putting them into a test setup and running code.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by sitkack on Thursday January 04, 2018 @01:02AM (#16068375)
Arm is a problem for all kernels not just Linux in how they map on chip peripherals, etc. All the problems that UEFI solve, are not solved on Arm.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by planteen on Wednesday January 03, 2018 @05:45PM (#16066101)
Yep. I've seen scary errata and had paranoid cache flushes in my code as a precaution.

My favorite ARM experience was where memcpy() was broken in an RTOS for "some cases". "some cases" turned out to be when the size of the copy wasn't a multiple of the cache line size. Scary stuff.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by HelloNurse on Wednesday January 03, 2018 @11:35AM (#16062411)
Obvious hypothesis: first complacency leads to incompetence, then starting to cut corners has catastrophic consequences. The two problems are wonderfully complementary.

As other comments suggest, there might be a third stage, completely forgetting how to design and validate chips properly.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by eximius on Wednesday January 03, 2018 @01:37PM (#16063674)
Or the system was designed poorly to begin with and now you're stuck with the design for backwards compatibility reasons.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by HelloNurse on Wednesday January 03, 2018 @03:31PM (#16064780)
I'd expect engineers that are aware of such serious bugs to spit on the grave of backwards compatibility. After all, the worst case impact would be smaller than the current emergency patches: rewriting small parts of operating systems with a variant for new fixed processors.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mtgx on Wednesday January 03, 2018 @11:20AM (#16062238)
I think that could also have been the "official reason".

The same reason could have been used to give the NSA some legroom for instance, but tell everyone that's why they won't do so much verification in the future.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by fpoling on Wednesday January 03, 2018 @12:27PM (#16062904)
This implies that ARM vendors do less validation. I guess ARM is just so much simpler that good enough validation can be done faster. So essentially this is payback time for Intel for keeping compatibility with older code and simpler to program architecture (stricter cache coherence etc.). It is like one can only have 2 of cheap, reliable, easy-to-program.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by pkaye on Wednesday January 03, 2018 @05:17PM (#16065818)
I'm sure ARM vendors have their own problems... it is just that they tend to be used in application specific products so the bugs are worked around. Having come from a firmware background I've worked are tons of ugly workarounds for serious bugs in validated hardware.

Furthermore, I just a read an article (can't find the link) that certain ARM Cortex cores have this same issues as Intel.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by lmm on Thursday January 04, 2018 @07:11AM (#16069746)
> This implies that ARM vendors do less validation. I guess ARM is just so much simpler that good enough validation can be done faster.

More likely "good enough" is much lower because ARM users aren't finding the bugs. The workloads that find these bugs in Intel systems are: heavy compilation, heavy numeric computation, privilege escalation attackers on multi-user systems. Those use cases barely exist on ARM: who's running a compile farm on ARM, or doing scientific computation on an ARM cluster, or offering a public cloud running on ARM?

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by leoc on Wednesday January 03, 2018 @10:59AM (#16062043)
Where’s that quote from? ISTR reading it (or something very similar) as reported speech in a HN comment.

Overall it’s a depressing story of predictable market failure as well as internal misbehavior at Intel, if true. Few buyers want to pay or wait for correctness until a sufficiently bad bug is sufficiently fresh in human memory. And if you do want to, it’s not as if you’re blessed with many convenient alternatives.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by deeth_starr_v on Wednesday January 03, 2018 @11:17AM (#16062215)
The quote is from the link above (referencing an anonymous reddit comment).
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mannykannot on Wednesday January 03, 2018 @10:46AM (#16061908)
That is a very interesting perspective, and as far as I know it is correct, though perhaps Intel's situation in the mobile market was exacerbated by complacency?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by djsumdog on Wednesday January 03, 2018 @01:40PM (#16063713)
There are people looking to deploy ARM servers now. However I wish there had been more server competition. Many companies write their backend services in Python, JVM (Java/Scala/Groovy), Ruby, etc. Stuff that would run fine on Power, ARM or other architectures. There are very few specialized libraries that really require x86_64 (like ffmpeg and video-transcoding)
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by astrange on Thursday January 04, 2018 @12:18AM (#16068233)
ffmpeg works great on ARM. I don't know if the PPC port is all that optimized lately.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by innagadadavida on Wednesday January 03, 2018 @11:04AM (#16062091)
But why do AMD chips not have similar issues? To me it looks like Intel tried to micro optimize something and screwed up.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rayiner on Wednesday January 03, 2018 @11:31AM (#16062367)
According to LKML: https://lkml.org/lkml/2017/12/27/2

> The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would result in a page fault.

Out-of-order processors generally trigger exceptions when instructions are retired. Because instructions are retired in-order, that allows exceptions and interrupts to be reported in program order, which is what the programmer expects to happen. Furthermore, because memory access is a critical path, the TLB/privilege check is generally started in parallel with the cache/memory access. In such an architecture, it seems like the straightforward thing to do is to let the improper access to kernel memory execute, and then raise the page fault only when the instruction retires.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by leoc on Wednesday January 03, 2018 @11:09AM (#16062132)
Maybe the answer lies in Intel’s feted IPC advantage over AMD? Or is it the case that AMD has simply been relatively lucky so far?
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by amigoingtodie on Wednesday January 03, 2018 @10:35AM (#16061794)
Sounds like Facebook and Youtube, too.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by devit on Wednesday January 03, 2018 @01:47PM (#16063794)
It depends on whether it's an attack against HVM hypervisors or not.

If it, like it seems, is just an attack on OS kernels and PV hypervisors, you can simply turn off the mitigation, since nowadays kernel security is mostly useless (and Linux is likely full of exploitable bugs anyway, so memory protection doesn't really do that much other that protecting against accidental crashes, which isn't changed by this).

Even if it's an attack against hypervisors any large deployment can simply use reserved machines and it won't have a significant cost.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Iv on Wednesday January 03, 2018 @08:09PM (#16067108)
More than the lawsuit, it attacks one of the core aspect of Intel's brand: performances. Intel chips are supposed to be faster. Now they are suddenly 30% slower because they carelessly implemented performance features over security ones.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by olfactory on Wednesday January 03, 2018 @11:34AM (#16062401)
> all companies paying for computing resources will have to pay roughly 30% more overnight on cloud expenses

Well, if I rent a VPS with x performance, I still expect x performance after this flaw is patched. The company providing the virtual machine will perhaps have to pay 30% more to provide me with the same product I've been getting.

Since most VPS offerings arbitrage shared resources, this will not increase costs of providing VPSes by the full performance penalty.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by tgarma1234 on Wednesday January 03, 2018 @12:17PM (#16062812)
But all you are ever getting with vps offerings is a description of the number of cpus and amount of ram and suchlike. I haven't seen vps offerings that say "x" chips yield "y" performance. Granted it is sort of implied that the hardware meets certain expectations but there isn't any guarantee. I was just now reading the TOS for AWS just to check and so far as I can tell they aren't guaranteeing any kind of specific performance.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by jk563 on Wednesday January 03, 2018 @11:52AM (#16062608)
Well if you use m5.xlarge instances from AWS you were getting 4 vCPUs for your money. I don't expect you'll now get 5...
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by olfactory on Wednesday January 03, 2018 @12:05PM (#16062707)
No, but the underlying hardware that perviously hosted two m5.xlarge instances may instead host one M5.xlarge and one M5.medium, so that performance is not degraded.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by sbarre on Wednesday January 03, 2018 @12:46PM (#16063091)
Yeah but AWS doesn't guarantee that "2x m5.xlarge" will meet any kind of performance requirements, particularly your own application's, do they?

So you may suddenly find that your own performance requirements, that were previously satisfied by "2x m5.xlarge" are no longer being met by that configuration, and I doubt AWS will just provide you with more resources at no additional charge.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Sean1708 on Wednesday January 03, 2018 @12:10PM (#16062742)
> Well, if I rent a VPS with x performance, I still expect x performance after this flaw is patched.

Are there any providers that state you will get x performance? Most that I've seen say you will m processors, n memory, and p storage but don't make any guarantees about how well those things will perform.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Retric on Wednesday January 03, 2018 @12:25PM (#16062881)
Last I checked Amazon AWS has a virtual processor metric not actual hardware metric. This is most noticeable in their lowest power instances which don't get a full modern CPU core.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by alanfalcon on Wednesday January 03, 2018 @01:49PM (#16063813)
If the virtual metric is tied to real performance then it could mean a drop in performance while maintaining the same power rating... It will be interesting to see if vendors directly address this.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by m3kw9 on Wednesday January 03, 2018 @11:22AM (#16062259)
Cloud services may not need to worry about the issue depending on the OS the customer choose to use, the patched or non patched version.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ajasmin on Wednesday January 03, 2018 @11:24AM (#16062284)
For the cloud providers it's the security of the hypervisor that's at stake.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by chrisper on Wednesday January 03, 2018 @11:30AM (#16062347)
Why would the OS of the customer matter? The patch would be applied to the kernel of the hypervisor / host OS.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ComodoHacker on Wednesday January 03, 2018 @12:42PM (#16063059)
Forgive me my ignorance, but I fail to see how this is such a big deal. Even 50% performance hit/cost increase would be... bearable, computations are rather cheap today. ML and other intensive calculations aren't done on CPU anyway. It's not like technical progress of our civilization is slowed down by 30% or something...

On the other hand, shrinking Intel's market share due to bad PR and thus adding some competition into the industry could actually foster that progress.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cdoxsey on Wednesday January 03, 2018 @12:47PM (#16063099)
If you run things efficiently you're eaking every ounce of performance out of this hardware. A 30% performance hit means a 30% cost increase.

The bigger issue is for things that don't scale easily. That sql server that was at 90% capacity is suddenly unable to handle the load. Sure that could've happened organically, but now it happens (perhaps literally) overnight for everyone all at once.

Expect a bunch of outages in the next few weeks as companies scramble to fix this.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ClassyJacket on Wednesday January 03, 2018 @03:36PM (#16064838)
"A 30% performance hit means a 30% cost increase."

Just wanna point out that a 30% performance hit means a 43% cost increase.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by planteen on Wednesday January 03, 2018 @05:52PM (#16066180)
Yes. This is so often forgotten when talking about stock prices (which those 2x or 3x daily derivatives are so dangerous).

For those confused: the math here is a 30% decrease puts you at 70%. To go from 70% back to 100%, 30% only gets you to 91% (0.70*1.3). 1/0.7 = 1.43 means you need 43% to recover.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mkagenius on Wednesday January 03, 2018 @02:46PM (#16064383)
Should the individual companies hurry to patch it. There is no news of exploit as such.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rkeene2 on Wednesday January 03, 2018 @04:14PM (#16065212)
There is now !
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by mkagenius on Thursday January 04, 2018 @12:14AM (#16068218)
Intel CEO added - "But when you take a look at the difficulty it is to actually go and execute this exploit — you have to get access to the systems, and then access to the memory and operating system — we're fairly confident, given the checks we've done, that we haven't been able to identify an exploit yet."

It seems you need root or physical access to the system as a prerequisite for the attack.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by ubernostrum on Thursday January 04, 2018 @05:29AM (#16069239)
You don't need root, and you don't need physical access. For Meltdown, you only need the ability to run your own code on the target machine.

Where that gets tricky is when everyone's using cloud hosting solutions where the physical machines are abstracted away, and a given physical server may be running multiple virtual servers for different customers.

Think of it like this:

* Somewhere in a data center at a cloud provider is a physical server, wired up in a rack..

* That server runs virtualization software, allowing it to host Virtual Server 1, Virtual Server 2, and Virtual Server 3.

* Virtual Server 1 belongs to Customer A. Virtual Servers 2 and 3 belong to Customer B.

* Normally, Virtual Server 1 can't access any memory allocated to Virtual Servers 2 and 3.

* BUT: Customer A can now use Meltdown to read the entire memory of the physical server. Which includes all the memory space of Virtual Servers 2 and 3, exposing Customer B's data to Customer A.

That's the threat here.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by djsumdog on Wednesday January 03, 2018 @01:47PM (#16063792)
Have you worked in a company where you've hit CPU performance limits. At my last job, we'd have some services run in 25 containers in parallel and we'd have to optimize as much as we could for performance bottlenecks. We'd literally get thousands of assets per minute some mornings, and had a ton of microservices to properly index tag, thumbnail and transcode them.

Our ElasticSearch nodes all had 32GB of ram and we had 10 of them and they were all being pushed to the max.

Something like this would be a massive hit, requiring a lot more work into identifying new bottlenecks and scaling up appropriately.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by cheeze on Wednesday January 03, 2018 @12:54PM (#16063202)
I think you're vastly underestimating the potential impact to cloud providers. Azure/AWS/GCP all definitely have extra capacity, but they have forecasting down to a science. Requiring even 10% more capacity is quite a large undertaking alone.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by LoSboccacc on Wednesday January 03, 2018 @02:48PM (#16064396)
Even the non provider side of google will see some impact and even 5% datacenter increase won’t happen overnight