Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Stress a page-walk and cache race

Hardware interview practice

Stress a page-walk and cache race

MediumComputer ArchitectureSystemVerilog

A hardware page walker shares the data cache while software can update page tables under the architecture’s synchronization rules. Which verification scenario adds the most value?

Try it in the question bankReason first. Then compare.

Keep this exact question selected while you check your answer and review the full solution.

Practice this question →
Choose one

Answer choices

  1. A. Verify only TLB hits after boot.
  2. B. Race page-table updates and required invalidation with cache eviction/writeback, permission faults, and a walk in flight.
  3. C. Randomize page-table memory while a walk runs, without executing the required architecture synchronization.
  4. D. Disable both the cache and MMU for every page-table test.
Continue practicing

Related questions

Computer ArchitectureRecognize write-back cache behavior→Computer ArchitecturePartition a cache address→Computer ArchitectureCalculate CPI with branch and cache penalties→
asic.fyi · Learn silicon end to end.info@asic.fyi