News for hackers. Stuff that matters.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by hayksaakian on Friday December 26, 2014 @08:13PM (#8801251)
I've noticed that CPU companies are focusing more and more on power efficiency to compete with ARM potentially. Maybe turning off the features described in the OP makes lower end CPUs run faster?

That might be significant since i also presume most laptops use those same lower end CPUs. Laptops being the ones that need to save energy much of the time. (Desktops are obviously plugged in).

This is probably most significant in the Microsoft Surface (it uses a real intel CPU if i recall correctly).

I wonder which features it has marked "off" , and what impact that has on battery power.

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Friday December 26, 2014 @09:15PM (#8801385)
Remember, within a generation these chips are almost all made from the same set of masks. None of these disabled features save any transistors or die area; the disabling just leaves you with a dead spot on the chip. So the real question is if you've got the hardware in place to provide these special features, can you save any power by not using those features?

The answer is that you only save power by not doing at all the things those features accelerate. It's never more efficient to implement AES through general-purpose instructions than using the fixed-function hardware. If you've got a workload that can benefit from the wider SIMD units, it won't save any energy to only use the narrower instructions. If you're trying to secure or virtualize your OS, doing it with VT-x and VT-d will be so much faster than emulating it in software that even if those features added several watts to the chips power consumption you would still save energy.

Doing less can save power, but doing the same amount of stuff the hard way doesn't help anything.

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by tanderson92 on Friday December 26, 2014 @09:27PM (#8801417)
That's only true if you are using those features 100% of the time though, right ? By which I mean, there is no doubt a trade-off in play when you only use the features for 15% of your workload. This is because the chip must be powered on all the time but, say, the software implementation of AES doesn't always have to be running.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Friday December 26, 2014 @10:03PM (#8801507)
No, special-purpose functional units are very well power-gated on modern chips. They don't draw appreciably more power when not in use than when fused off.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by rasz_pl on Saturday December 27, 2014 @12:47PM (#8803250)
you say that, but in practice Intel is still 5-10x off ARM when it comes to idle power.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Saturday December 27, 2014 @06:37PM (#8804417)
Register renaming and instruction reordering and things like that can't be selectively powered down, and are very power-hungry. But if you were talking about when the entire core is suspended, then that's largely unrelated to the high-level feature set of the processor. It's about things like the analog characteristics of the transistors used: Intel builds their mainstream CPUs using circuits that can run at 4-5GHz without trouble while none of the mobile SoCs can come close regardless of exotic cooling.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wmf on Saturday December 27, 2014 @01:25PM (#8803392)
Is that true for Merrifield/Moorefield? AFAIK they're pretty close, but only in the phone chips.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by nkurz on Saturday December 27, 2014 @04:13PM (#8803950)
Remember, within a generation these chips are almost all made from the same set of masks. None of these disabled features save any transistors or die area

I think it might be true for CPUID/stepping, but not for what are usually considered to be the generations.

For example, there look to be at least 5 dies sizes for Sandy Bridge: http://en.wikipedia.org/wiki/Sandy_Bridge#Models_and_steppin...

I haven't tried to match up the supported ISA's with the different die sizes, but I presume they'd correlate. Do they not?

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Saturday December 27, 2014 @05:48PM (#8804263)
The quad-core Sandy Bridge could end up labeled as a Core i5, Core i7, or Xeon E3. The dual core Sandy Bridge could be labeled as a Pentium, Celeron, Core i3, Core i5, Core i7 (mobile), or Xeon E3.

The server designs (LGA2011) have QPI links and may be the only memory controllers capable of using registered memory. But among the processors targeting the LGA1155 and mobile platforms, they only had one core design and only one memory controller design that was shared across all products though never with everything enabled at once.

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by nkurz on Saturday December 27, 2014 @06:29PM (#8804388)
Yes, I agree, number of cores and size of L3 are commonly cases cases where functionality is disabled. But do you know which of the other factors listed in the article that this is true for? For example, are there cases where two processors share the same die but one supports AVX and the other does not? I don't know the answer, but if there are not, this would substantially undercut the argument in the main article.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Saturday December 27, 2014 @06:49PM (#8804446)
Sandy Bridge and Ivy Bridge Celerons and Pentiums use the same die as the corresponding Core i3s, but only the i3 supports AVX in the CPU and QuickSync in the GPU. AES instructions aren't available on the i3 but are present on the dual-core i5. Haswell no longer discriminates with QuickSync, and extends AES down to the i3s but still not the Celerons and Pentiums.

None of these features are unavailable due to being physically absent. They're just turned off. If Intel's microcode format and DRM were reverse engineered, some of the features could be turned back on.

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by nkurz on Saturday December 27, 2014 @09:32PM (#8804928)
Thanks for the great info. That was the part I couldn't figure out from the article or the specs.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by vardump on Saturday December 27, 2014 @08:03PM (#8804672)
Artificially disabling ECC (error correcting) SDRAM support is very disappointing. In my experience ECC significantly improves stability. Laptops (without ECC RAM) crash a few times per year, desktops with ECC RAM can run stable for years.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by dippyskoodlez on Friday December 26, 2014 @10:25PM (#8801556)
You can also disable defective components without being forced to bin the entire chip to a recycle bin.

That is honestly probably more of a factor than anything for the segregation between models. Get that yield up to improve margins significantly.

Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by wtallis on Friday December 26, 2014 @10:35PM (#8801583)
Disabling whole cores or lumps of cache to improve yields is one thing, but a lot of the features Intel is segmenting the market with are very tightly integrated with the rest of the chip. It would be extremely hard to detect and classify a defect as affecting HyperThreading or VT-x but leaving the core otherwise functional. It's a bit more plausible that defects in the high half of a vector SIMD unit could leave you with a SSE-capable but AVX-defective chip, but I suspect that in practice any broken functional units are treated as rendering the entire core inoperable.
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by icegreentea on Friday December 26, 2014 @08:26PM (#8801276)
The "lowest" end of the CPUs that the OP discusses are low end desktop/laptop parts. Furthermore, the biggest criticism of the author isn't the feature disabling per se, but how inconsistently Intel applies it across their overall performance bins. For example, the lack of TXT support in high end i7 parts when its there for middle tier i5 parts. Why the i7-3990K has VT-d and the i7-3770K doesnt(which really should just be distinguished by their clock/cache/TDP).
Re:Sandy bridge, Ivy bridge, Haswell and the mess of Intel p... by ptysiu on Sunday December 28, 2014 @04:10AM (#8805819)
3770K cpu has basic version 3770, which has the VT-d ext. There is no such thing like 3990k.