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

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

    Interface ProtocolsAll levels

    Snoop & Cache Maintenance: Interview

    Interview for Snoop & Cache Maintenance.

    Interview drills

    Can a CPU barrier alone replace the DMA mapping and cache-maintenance contract for a non-coherent device?

    Check yourself Can a CPU barrier alone replace the DMA mapping and cache-maintenance contract for a non-coherent device?

    No. Ordering a CPU’s operations does not by itself make the required bytes visible across a non-coherent path. Use the platform DMA lifecycle and ownership rules.

    Common trap: Giving a generic fix without identifying the boundary and unmet obligation in this example.

    What does Shared state mean in MESI?

    Check yourself What does Shared state mean in MESI?

    Line is valid and may exist in multiple caches. Reads are allowed from any copy. Writes require upgrading to Modified, which invalidates other copies. It's not the same as Exclusive — Exclusive means only one cache has a clean copy.

    Common trap: Confusing Shared with Exclusive.

    Previous

    54 / 158

    Next: CHI Topology Basics

    Up next

    Up nextCHI Topology Basics

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Snoop & Cache Maintenance: Concepts
    • Snoop & Cache Maintenance: Integration