1. 13 6月, 2020 1 次提交
  2. 24 12月, 2019 2 次提交
  3. 14 12月, 2019 1 次提交
  4. 22 11月, 2019 1 次提交
  5. 18 11月, 2019 1 次提交
  6. 15 11月, 2019 5 次提交
  7. 07 11月, 2019 2 次提交
  8. 31 10月, 2019 1 次提交
  9. 29 10月, 2019 1 次提交
  10. 22 10月, 2019 1 次提交
  11. 07 10月, 2019 5 次提交
  12. 05 10月, 2019 1 次提交
  13. 01 10月, 2019 1 次提交
  14. 22 9月, 2019 1 次提交
  15. 19 9月, 2019 1 次提交
  16. 15 9月, 2019 1 次提交
  17. 07 9月, 2019 3 次提交
  18. 06 9月, 2019 1 次提交
    • Z
      system,Coherence: handle coherence read from ICache · 52ed0a6f
      Zihao Yu 提交于
      * Now it will easily cause deadlock because the coherece probe requests
        are handled with the same pipeline of CPU access requests. When the
        Dcache is processing a miss request, it may form the following loop
        dependency:
          Icache.mem.resp -> CoherenceInterconnect.in(0).coh.resp ->
          Dcache.mem.resp -> CoherenceInterconnect (busy)
      * To break the deadlock, we should give higher priority to coherence
        probe requests in L1 Cache. For example, we should add another state
        machine or pipeline to handle coherence probe requests. In this way,
        the coherence probe requests can be handled without waiting for the
        CPU access requests to finish.
      52ed0a6f
  19. 03 9月, 2019 1 次提交
  20. 01 9月, 2019 2 次提交