Silicon development and software development operate on very different timescales.
An advanced processor may take years to architect, design and qualify. During its operational lifetime, the software running on it can change repeatedly.
For AI hardware, that creates a difficult power-integrity problem.
A new model may exercise processing elements in a different pattern from anything used during initial silicon characterisation. Those changes in switching activity can alter current demand and expose voltage-droop conditions that were not obvious on the bench.
What causes voltage droop?
A processor does not draw a constant current.
As cores, accelerators and memory interfaces change state, demand on the Power Delivery Network can rise rapidly.
If the PDN cannot supply that change immediately, the local supply voltage falls.
Movellus compares this behaviour to a resonance. Particular combinations of silicon, package, board and workload can create especially difficult transient conditions.
The result may be a temporary performance problem. In more severe cases, timing margins can be compromised.
Movellus also identifies silent data corruption as a potential consequence. Unlike a system crash, silent data corruption can allow execution to continue while producing an incorrect result.
Why traditional guardbands cost performance
One approach is to add more voltage margin.
If engineers do not know exactly how low the voltage may fall under future workloads, they can raise the operating voltage to create additional safety margin.
That improves resilience, but costs power.
Voltage is particularly expensive because dynamic power has an approximately quadratic relationship with supply voltage.
Reducing unnecessary guardband therefore creates an opportunity to improve energy efficiency or recover additional performance.
Responding before firmware can react
Voltage droop can occur on nanosecond timescales.
A conventional software control loop is too slow to detect a transient, make a decision and adjust the system before the event has already occurred.
Movellus addresses this through its Aeonic Integrated Droop Response System.
An Aeonic Insight sensor detects the event on-die. That information is passed directly into an Aeonic Generate adaptive clock, which can reduce frequency without waiting for a firmware decision.
Once the supply recovers, the clock can be ramped back towards its original operating point.
Movellus says the integrated system responds in fewer than three high-speed clock cycles.
Characterising workloads after deployment
Fast response solves one part of the problem. Engineers also need to know what actually happened.
This is where Aeonic Insight PDN IQ is relevant.
The IP places sensors across the silicon to provide transistor-level PDN telemetry. Engineers can monitor voltage behaviour as real workloads run and capture statistics or traces when defined thresholds are crossed.
This changes the characterisation model.
Instead of relying entirely on the workloads available before deployment, teams can inspect how future software affects the power plane on deployed silicon.
That information can then be used to refine operating points and voltage-frequency settings.
From data centre to edge AI
The immediate pressure is obvious in large AI and data-centre systems, where power density and utilisation are already high.
The same engineering problem can become relevant elsewhere as increasingly capable AI models move into automotive, PCs and edge devices.
Those systems generally have tighter thermal and power budgets, making unnecessary voltage margin even more expensive.
The engineering requirement remains the same: understand what the workload is doing to the silicon and respond quickly when the operating conditions change.
For Movellus, that means treating the power plane as an active part of the architecture rather than a fixed constraint established during initial characterisation.
Comments are closed.
Comments
No comments yet