22,096 karma · joined September 20, 2009
What needs to fail here is the instruction doing insanely slow MMIO. That's not going to be too hard to debug; none of the examples of suitably slow instructions are anywhere close to reasonable, and a fault on a vmovdqu in MMIO address space is a big red flag.
And this attack requires enough ridiculous behavior from coordinating software beyond just the single super-slow instruction that it's hard to imagine any reasonable workload being affected if this case starts causing a fault.
The base interface die has eight or 12 memory dies stacked on top of it. The wafer cost of that interface die is therefore small.
If the process of die thinning and TSV stacking reduced yields by a factor of three, nobody would consider HBM mature enough to put into production, and especially not mature enough to be increasing stack height from one generation to the next.
Trace length has approximately nothing to do with die size. If anything, designing for shorter traces means you can get away with smaller PHYs at either end.
What might go some ways toward explaining such a huge difference in die size is that the TSVs themselves take up significant die area and must be fairly numerous to carry both a large number of signal wires and all the power and ground required by the stack. But it's wildly implausible that the die area consumed by the TSVs would be significantly larger than the die area consumed by the memory arrays themselves, or that anyone would build a memory die where the memory array was not a large majority of the total die area.
If there's any truth to that ~3x higher wafer requirement for the same number of bits as compared to DDR5, it must be a combination of several factors and probably includes something non-obvious and dubious, like counting all the area of the passive interposers that go between HBM stacks and GPUs (those interposers aren't competing for the same fab space).
Did you mean that each HBM3 stack is that large? Because it only takes one glance to see that the memory chips are much smaller than reticle-sized GPUs they sit next to.
You could try reading the footnotes, which include a link to https://www.amd.com/content/dam/amd/en/documents/solutions/a...
This announcement is for a system to do the first phase on Helios and the second phase on WSE.
Geekbench has that as a subtest.
> For the other multi-threaded tasks, like running certain CAD/EDA applications, I use well-optimized programs, either by others or by myself.
Those seem pretty clearly out of scope. You want a workstation benchmark, not a consumer benchmark.
> This would be fine, if it would be more clearly specified when the Geekbench benchmark is distributed.
The descriptions of what Geekbench is are adequate. You're asking for Geekbench to exhaustively list what it isn't to stop you from imagining it to be a one-size-fits-all benchmark, which couldn't possibly exist.
> But others appear to not be aware of this and I have seen frequently erroneous claims on the Internet that some laptop or even some smartphone would match or exceed the performance of a desktop or of a bigger laptop, even one with a CPU with more cores, based on the published Geekbench multi-threaded results, while in reality that desktop or big laptop has a much greater throughput.
Again you seem to be unable to stop asserting that workstation or server use cases are the only ones that are real.
You're contradicting yourself. Do you want realistic scaling, or the kind of highly-tuned hand-optimized scaling that almost no real-world applications (especially in the consumer space) ever get?
In both of your comments here, you make very narrow assumptions about what constitutes a "real" workload, and you're excluding ordinary everyday consumer PC software from what you consider "real". Highly optimized software running on large servers aren't the only "real" workloads, and they're not the kind of "real" workload that Geekbench is trying to represent. For the kind of hardware and use cases that Geekbench actually targets, using the platform/compiler default synchronization primitives and doing work in short bursts interspersed with significant idle time is reasonable and realistic.
SPEC CPU is distributed in source form, to be compiled by the end user. There are restrictions on what kind of compiler options and other games you can play when making an official submission to SPEC, which Intel (and others) get around by publishing "estimated" SPEC scores and using those for marketing claims. In practice, the amount of bullshit in Intel's claimed SPEC scores is constrained only by what Intel's legal department is willing to risk getting sued over.
Geekbench is distributed in binary-only form with all binaries for all platforms originating from the author of Geekbench. All the major chip designers pay to see the source code and participate in the development, but the final decisions about what code goes in and how it's compiled are made by the author of Geekbench, not by the chip vendors. They just get to lobby, and AMD has every opportunity to call out Intel and Geekbench should the compiler options for the x86 builds be unfair.
Intel has a long history of cheating on SPEC, but cheating on Geekbench is more difficult because of the necessity of runtime binary patching and they didn't publicly try until this year, with limited success and lots of negative press: https://www.geekbench.com/blog/2026/03/geekbench-6-and-intel...
(One could just as easily argue that the single-core test suite ought to exclude any task typically done with multiple threads in real-world usage.)
Yes, that's pretty much the whole point of Geekbench: to offer non-experts a way to measure CPU performance and produce scores that are relevant to a specific class of devices and users and use cases, rather than artificially inflated.
Benchmarking experts can already use something like SPEC, which does offer single-thread and both types of multi-thread test modes (SPECrate and SPECspeed).
The Geekbench 5 approach of pretending Amdahl's Law doesn't exist is sometimes a valid benchmarking strategy, but generally is the wrong choice for benchmarking consumer workloads and devices, and that's what Geekbench is ostensibly targeting.
The fact that Geekbench 6 scores don't increase linearly with the addition of more CPU cores is not a weakness of the benchmark, it's the benchmark demonstrating an important real-world effect.
The change that Geekbench 7 makes to exclude some subtests from the multicore suite entirely will definitely have the effect of making the overall multicore score scale better with the addition of more cores, but most of the audience for those scores is going to miss out on the fact that the multicore test now measures a narrower range of tasks than the single-core test suite.
Doesn't the argument work fine on the CPU side? Apple doesn't seem to be hurting for lack of a Threadripper competitor.