1. 23 Aug, 2022 1 commit
  2. 22 Aug, 2022 1 commit
  3. 12 Aug, 2022 1 commit
  4. 11 Aug, 2022 2 commits
  5. 10 Aug, 2022 3 commits
  6. 09 Aug, 2022 1 commit
  7. 31 Aug, 2021 1 commit
  8. 15 Oct, 2020 2 commits
  9. 05 Oct, 2020 2 commits
  10. 21 Aug, 2020 2 commits
  11. 10 Aug, 2020 3 commits
  12. 22 Jul, 2020 1 commit
  13. 20 Jul, 2020 1 commit
  14. 16 Jul, 2020 1 commit
  15. 03 Oct, 2019 1 commit
  16. 10 Sep, 2019 1 commit
  17. 18 Aug, 2019 1 commit
  18. 30 Jul, 2019 1 commit
  19. 29 Jul, 2019 1 commit
    • Frans Kaashoek's avatar
      Remove B_DIRTY · 53043104
      Frans Kaashoek authored
      Use refcnt to pin blocks into the cache
      Replace flags/B_VALID with a boolean field valid
      Use info[id].status to signal completion of disk interrupt
      Pass a read/write flag to virtio_disk_rw
      53043104
  20. 28 Jul, 2019 1 commit
  21. 27 Jul, 2019 1 commit
  22. 26 Jul, 2019 1 commit
  23. 25 Jul, 2019 1 commit
  24. 24 Jul, 2019 2 commits
  25. 23 Jul, 2019 2 commits
  26. 22 Jul, 2019 1 commit
  27. 19 Jul, 2019 1 commit
    • Frans Kaashoek's avatar
      One way of supporting a guard page below kstack: allocate kstacks in · 91566327
      Frans Kaashoek authored
      procinit() and map them high up (below TRAMPOLNE) with an empty
      mapping below each stack.  Never free a kernel stack.
      
      Another way would be to allocate and map them dynamically, but then we
      need to reload page table when switching processes in scheduler()
      and/or have a kernel pagetable per proc (if we want k->stack to be the
      same virtual address in each process).
      
      One gotcha: kernel addresses are not equal to physical addresses for
      stack addresses.  A stack address must be translated if we need its
      physical address (e.g., virtio passes a stack address to the disk).
      91566327
  28. 02 Jul, 2019 1 commit
  29. 01 Jul, 2019 1 commit
  30. 13 Jun, 2019 1 commit