Got it. Yeah, same thing about MCM versus monolithic in the other camp. Not everybody says it or thinks it though, for either subject. Just business.
To be clear though, we didn't say MCM was bad, we said *unconnected* MCM was bad.
There are benefits of MCM that Intel brought up and we agreed with (time to market, yield, etc.) But there was a big downside of an unconnected MCM which was higher bus traffic, latency and system bottlenecks.
Most of the time that I criticized MCM, the sound bite that made it into the publication was simplified to "MCM is bad" and the subtlety of what I had said was lost. We had MCM on the roadmap at the time that we were making the statements, so that was always in the backs of our minds.
Limiting speed bin, core or cache is fine. The speed bin sorting has been going on for years in the industry. However, limiting features like HT, virtualization or turbo generally lead to more customer confusion. People expect to get X and end up with Y. They can't understand why applications perform differently.
I guess if I had to categorize it, I would group things into "obvious" and "not obvious". When you buy a processor in a system, you see the clock speed, cores and cache listed. Those are obvious and easy for people to understand. Some of the other things are less obvious and more difficult for people to understand what they have/don't have. Not an issue as much for consumers as it is in a data center where you have hundreds or thousands of servers with dozens of different configurations.