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

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Protocol Metrics Reference
  • Protocols Glossary
  • Reading Path
  • Protocol Fundamentals25
  • AMBA Family (APB / AHB / AXI)17
  • Coherence Fabrics (ACE / CHI)17
    • ACE Coherent Transactions
    • Snoop & Cache Maintenance
      • Snoop & Cache Maintenance: Concepts
      • Snoop & Cache Maintenance: Integration
      • Snoop & Cache Maintenance: Debug
      • Snoop & Cache Maintenance: Interview
    • CHI Topology Basics
    • Coherence Fabric Debug
    • Coherence Fabrics (ACE / CHI): Tricky Q&A
  • Memory Interfaces (DDR / LPDDR / HBM)17
  • PCIe & CXL17
  • Embedded Peripherals (I2C / SPI / UART)17
  • High-Speed I/O (USB / Ethernet / MIPI)17
  • Protocol Verification & Compliance21
  • Protocols Interview Prep5
  • Interface Protocols Cheatsheet
Loading lesson

←Coherence Fabrics (ACE / CHI)
  1. Topics
  2. Bus Protocols
  3. Coherence Fabrics (ACE / CHI)
  4. Snoop & Cache Maintenance
On this page

    Interface ProtocolsAll levels

    Snoop & Cache Maintenance

    Cache lines move through states (MESI). Snoops and maintenance ops control those transitions.

    • 4topics
    • 4lessons

    What you'll learn

    Cache lines move through states (MESI). Snoops and maintenance ops control those transitions.

    • MESI states: Modified, Exclusive, Shared, Invalid — define what operations are legal.

    • Cache-maintenance operation names, target points and completion rules come from the selected architecture and platform.

    • DMA and memory-attribute transitions use platform ownership, mapping, maintenance and synchronisation contracts rather than one universal flush sequence.

    Connection

    Cache state theory applied to ACE/CHI snoop transactions.


    Key diagram

    Maintenance follows ownership, not a universal flush recipe

    Maintenance follows ownership, not a universal flush recipe. Platform APIs define the required direction and lifecycle operations. Coherence, maintenance and software ordering are separate obligations.
    Platform APIs define the required direction and lifecycle operations. Coherence, maintenance and software ordering are separate obligations.
    Check yourself Does a coherent path let you skip publishing ownership in the software contract?

    No. It can remove some maintenance work but does not replace synchronisation and ownership transfer.


    Study this topic

    1. Concepts — rules and mental models

    2. Integration — system contracts

    3. Debug — trace the first divergence

    4. Interview — explain and defend your answer

    PreviousNext: Snoop & Cache Maintenance: Concepts

    Up next

    Up nextSnoop & Cache Maintenance: Concepts

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • ACE Coherent Transactions
    • CHI Topology Basics
    • Coherence Fabric Debug