I'm really curious how Intel could even imagine this is enforceable. For instance, if I have a server with shell access for many users, am I supposed to forbid my users from publishing benchmarks? If they do, am I liable since I "agreed" to the license? Or are they, even though they never "agreed" to the license? It just doesn't make sense.
Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
31–40 of 499 posts
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#32Has Intel just outlawed any review website (gaming, enthusiast, etc) from ever posting benchmarks of their CPUs again? I feel like they didn't think this through.
And even if they did think it through. It should be aggressively ignored.
[Sure it's not going to fly given Intel's market position, but it's a tempting thought anyway...]
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#33This TOS is driven by lawyers, not by business decision makers
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#34They better be wary of the Streisand Effect here. Banning benchmarking just makes it seem like the performance hit is going to be serious, which makes everyone even more curious.
I didn't know anything about this... now I'm really curious what the benchmarks are. Now that it is news they're pretty much begging for someone to do the benchmarks. This reminds me of the oracle license that was so broad it prevented users from talking to other users about their experience with the product... any experience.
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#35Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#36As a side note: Some of the license changes also block Debian from updating their intel-microcode package[1]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906158#14
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#37Aside from my vic20 and c64 I’ve only ever owned intel CPUs, and those two may have been intel as well, I wouldn’t know. I’ve never made a decision to chose Intel based on benchmark, I’ve bought them because they’ve always been great for me. So it’ll be ironic when I buy an AMD processor when I upgrade for cyberpunk 2077, because of benchmarks. Not because AMD is faster, they may be but I wouldn’t know, no, it’ll be…
At that time, few home computers were based on Intel processors because they were too expensive. Commodore's early computers, like Atari's, were based on the MOS Technology 6502 (made by ex-Motorola engineers as a cheaper and easier-to-integrate alternative to the Motorola 6800; the corresponding Intel-killer was the Zilog Z80 notably used in various CP/M and MSX computers). Commodore eventually acquired the company, rebranding it Commodore Semiconductor Group. A CMOS version of the 6502 is still sold by the Western Design Center [1].
Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#38Re: Intel Publishes Microcode Patches, No Benchmarking or Comparison Allowed
#39I can think of two theories: 1. It's a mistake. Someone in legal got carried away. 2. The performance of the L1TF mitigation is so awful that someone at Intel thought it would be a good idea to try to keep the performance secret. (Which leads to option 2b. The performance of the L1TF mitigation is so awful that somemone at Intel is afraid that Intel could be sued as a result, and they want to mitigate that risk.) I w…