Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Architecture Metrics Reference
  • Workload Taxonomy for Architects
  • Architecture Glossary
  • Computer Architecture Cheatsheet
  • Pipeline Fundamentals14
  • Memory Hierarchy15
  • NoC and Interconnect Architecture6
  • Coherency and Memory Ordering9
  • Performance Analysis9
  • Accelerator Architectures6
  • SoC Architecture Tradeoffs9
    • PPA at System Level
      • PPA Budget Ledger
      • Workload-Weighted Model
      • Floorplan-Aware Budgets
      • Budget Negotiation
      • Architecture Signoff
    • Power and Energy for the Architect
  • Architecture Interview Prep14
Loading lesson

‹PPA at System Level
  1. Topics
  2. Computer Architecture
  3. SoC Architecture Tradeoffs
  4. PPA at System Level
  5. Budget Negotiation

Computer Architecture · All levels

Budget Negotiation

Negotiate budget deltas with evidence, V-F arithmetic and cumulative margin discipline.

On this page

    The ledger is the contract

    Every request states baseline, delta, confidence and owner. The snapshot below is illustrative and follows the ledger format.

    Diagram
    BUDGET NEGOTIATION SNAPSHOT (illustrative, release chip_budget_r6)
      requested_perf_delta .. +7.5%
      approved_perf_delta ... +3.0%
      grant rate = 3.0 / 7.5 = 0.40 -> 40% of ask
      power = +140 mW on 4200 -> 140 / 4200 = 3.33% -> +3.3%
      area  = +1.8 mm2 on 146.0 -> 1.8 / 146.0 = 1.23% -> +1.2%
      new totals = 4340 mW, 147.8 mm2
      verification = +0.5 wk on a 10 wk plan -> +5%
      unresolved_items = 2 (each with owner and due date)

    Unresolved items gate the decision, not the slides. Two open items with owners mean conditional approval at best.

    Frequency-voltage-power trade

    Dynamic power follows P = C x V^2 x f. A frequency ask without a voltage statement is not a proposal.

    Diagram
    Plus 120 MHz on a 1500 MHz base (illustrative, CPU dynamic 1500 mW)
      f ratio = 1620 / 1500 = 1.08 -> +8% dynamic at fixed V
      fixed-V cost = 0.08 x 1500 = +120 mW
      with +40 mV on 0.80 V: (0.84 / 0.80)^2 x 1.08 = 1.1025 x 1.08 = 1.1907
      raised-V cost = 0.1907 x 1500 = +286 mW (about +19%)

    Option

    Power cost

    Verdict

    Raise V to hold timing

    +286 mW

    reject unless offset elsewhere

    Hold V, cut activity 8%

    +0 mW net

    approve with workload proof

    Reject the request

    +0 mW

    default when envelope is exhausted

    Cumulative margin discipline

    Small exceptions sum. Six approvals of 0.8% consume 4.8% before anyone feels nervous.

    Diagram
    Cumulative exceptions vs a 5% guardband (illustrative, 4200 mW base)
      six small = 6 x 0.8% = 4.8% = 6 x 33.6 = 201.6 mW
      seventh ask = +1.0% = 42.0 mW
      cumulative = 201.6 + 42.0 = 243.6 mW
      guardband = 0.05 x 4200 = 210 mW
      243.6 > 210, so the seventh ask escalates

    The rule is mechanical: track the cumulative sum against the guardband. Crossing it escalates regardless of how small the latest ask looks.

    Common mistakes

    Common pitfall

    Teams reporting on incompatible measurement windows agree on nothing while sounding aligned. Fix one definition set and one reference corner before comparing any two deltas.

    Interview

    Likely probes: technical-not-political negotiation.

    • Convert every ask into baseline, delta, confidence and owner.

    • Run the V-F arithmetic before discussing schedule.

    • Reject a tiny exception when the cumulative sum breaches the guardband.

    Check yourself A 7.5% ask is granted 3.0% with +140 mW on a 4200 mW base. What are the grant rate and the power delta?

    Grant rate 40%, power delta +3.3%, for a new total of 4340 mW.

    Check yourself Six 0.8% exceptions are approved and a seventh asks 1.0% against a 5% guardband. What happens?

    The cumulative 5.8% exceeds the guardband, so the seventh ask escalates.

    Related topics

    • Interview method and scenarios

    • SoC course

    Previous

    67 / 86

    Next: Architecture Signoff

    Up next

    Up nextArchitecture Signoff

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • PPA Budget Ledger
    • Workload-Weighted Model