Let's write an OS which can run on RISC-V in Rust from scratch!
Go to file
2021-11-20 15:31:39 +08:00
bootloader Update rustc && rustsbi-k210 2021-08-26 21:03:50 +08:00
easy-fs Rm spin::Mutex except for easy-fs & add new test huge_write & flush cache to disk after a write transaction 2021-07-21 19:10:04 +08:00
easy-fs-fuse User base from 0x0->0x10000; user image size limit from 128MB->16MB; trigger race condition on k210 2021-10-03 07:36:41 -07:00
os Now construction of PA/VA only uses 56/39 bits. 2021-11-13 03:06:44 -08:00
user Implement mpsc using semaphores. 2021-10-10 17:20:53 -07:00
.dockerignore Add Ubuntu18.04 docker 2021-02-28 06:33:45 +08:00
.gitignore update .gitignore README.md dev-env-info.md 2021-11-20 15:31:39 +08:00
dev-env-info.md update .gitignore README.md dev-env-info.md 2021-11-20 15:31:39 +08:00
Dockerfile Add Ubuntu18.04 docker 2021-02-28 06:33:45 +08:00
LICENSE Initial commit 2020-10-29 15:21:09 +08:00
Makefile Add Ubuntu18.04 docker 2021-02-28 06:33:45 +08:00
README.md update .gitignore README.md dev-env-info.md 2021-11-20 15:31:39 +08:00
rust-toolchain rust->nightly-2021-10-15,cargo-binutils->0.3.3 2021-10-20 13:49:12 -07:00

rCore-Tutorial-v3

rCore-Tutorial version 3.5. See the Documentation in Chinese.

news

  • 2021.11.20: Now we are updating our labs. Please checkout chX-dev Branches for our current new labs. (Notice: please see the [Dependency] section in the end of this doc)

Overview

This project aims to show how to write an Unix-like OS running on RISC-V platforms from scratch in Rust for beginners without any background knowledge about computer architectures, assembly languages or operating systems.

Features

  • Platform supported: qemu-system-riscv64 simulator or dev boards based on Kendryte K210 SoC such as Maix Dock
  • OS
    • concurrency of multiple processes
    • preemptive scheduling(Round-Robin algorithm)
    • dynamic memory management in kernel
    • virtual memory
    • a simple file system with a block cache
    • an interactive shell in the userspace
  • only 4K+ LoC
  • A detailed documentation in Chinese in spite of the lack of comments in the code(English version is not available at present)

Run our project

TODO:

Working in progress

Now we are still updating our project, you can find latest changes on branches chX-dev such as ch1-dev. We are intended to publish first release 3.5.0 after completing most of the tasks mentioned below.

Overall progress: ch7

Completed

  • automatically clean up and rebuild before running our project on a different platform
  • fix power series application in early chapters, now you can find modulus in the output
  • use UPSafeCell instead of RefCell or spin::Mutex in order to access static data structures and adjust its API so that it cannot be borrowed twice at a time(mention & .exclusive_access().task[0] in run_first_task)
  • move TaskContext into TaskControlBlock instead of restoring it in place on kernel stack(since ch3), eliminating annoying task_cx_ptr2
  • replace llvm_asm! with asm!
  • expand the fs image size generated by rcore-fs-fuse to 128MiB
  • add a new test named huge_write which evaluates the fs performance(qemu~500KiB/s k210~50KiB/s)
  • flush all block cache to disk after a fs transaction which involves write operation
  • replace spin::Mutex with UPSafeCell before SMP chapter
  • add codes for a new chapter about synchronization & mutual exclusion(uniprocessor only)

Todo(High priority)

  • support Allwinner's RISC-V D1 chip
  • bug fix: we should call find_pte rather than find_pte_create in PageTable::unmap
  • bug fix: check validity of level-3 pte in find_pte instead of checking it outside this function
  • use old fs image optionally, do not always rebuild the image
  • add new system calls: getdents64/fstat
  • shell functionality improvement(to be continued...)
  • give every non-zero process exit code an unique and clear error type
  • effective error handling of mm module

Todo(Low priority)

  • rewrite practice doc and remove some inproper questions
  • provide smooth debug experience at a Rust source code level
  • format the code using official tools

Crates

We will add them later.