Dev yys pa3.1

[yanyusong57]

PA3.1 translated

[yifeifang]

Suggested change

	The von Neumann computer was indeed so powerful that it was able to give new life to cold gate circuits. In order to allow the computer to automatically run a set of programs, the pioneers improved the computer.
	The von Neumann computer was indeed so powerful that it was able to bring the gate circuits to life. In order to allow the computer to automatically run a set of programs, the pioneers improved the computer.

[yifeifang]

use md style -

[yifeifang]

Suggested change

	**Expected average time to completion**: 40小时
	**Expected average time to completion**: 40 hours

[yifeifang]

Suggested change

	* task PA3.2: Implement the loading and system calling of user programs, and support the running of TRM programs
	* task PA3.2: Implement the loading of guest program and system calls, and support execution of TRM programs.

[yifeifang]

Suggested change

	* task PA3.3: Run Xian Jian Qi Xia Zhuan (also called Chinese PAL) and Fairy and demonstrate the batch processing system, and submit a complete experimental report
	* task PA3.3: Run Xian Jian Qi Xia Zhuan (also called Chinese PAL) and demonstrate the batch processing system, and submit a complete lab report

[yifeifang]

Suggested change

	#### What is an operating system? (It is recommended to think about it in the second trail)
	#### What is an operating system? (It is recommended to think about it in the second round)

[yifeifang]

Suggested change

Nanos-lite contains all modules used in subsequent PAs, but the specific functions of most modules have not been implemented. Since the functions of the hardware (NEMU) are gradually added, Nanos-lite must also cooperate with this process. You will use some macros in `nanos-lite/include/common.h` which are used to control the functions of Nanos-lite during the experiment. As the experimental progress progresses, we will gradually explain all the modules, and Nanos-lite will do more and more work. Therefore, when reading the code of Nanos-lite, you only need to care about the modules related to the current progress, and do not get entangled in the code that is not related to the current progress.

Nanos-lite contains all modules used in subsequent PAs, but the functionality of most modules has not yet been implemented. Since the functionality of the hardware (NEMU) are gradually added, Nanos-lite must align with it. You will use some macros in `nanos-lite/include/common.h` which controls the feature set based on your progress. As the lab progresses, we will gradually explain all the modules, and Nanos-lite will do more and more work. Therefore, when reading the code of Nanos-lite, you only need to care about the modules related to the current progress, and do not get trapped in the code that is not related to the current progress.

[yifeifang]

Suggested change

It should be reminded that Nanos-lite runs on AM, and AM’s APIs are available in Nanos-lite. Although the operating system is a special concept to us, from AM's perspective, it is just an ordinary C program that calls the AM API, no different from Super Mario. At the same time, you will once again realize the benefits of AM: the implementation of Nanos-lite can be architecture-independent, which means that no matter which ISA you have chosen before, you can easily run Nanos-lite, and even you can Just like developing klib, debug your Nanos-lite on `native`.

It should be reminded that Nanos-lite runs on AM, and AM’s APIs are available in Nanos-lite. Although the operating system is a special concept to us, from AM's perspective, it is just an ordinary C program that calls the AM API, no different from Super Mario. At the same time, you will once again realize the benefits of AM: the implementation of Nanos-lite can be architecture-independent, which means that no matter which ISA you have chosen before, you can easily run Nanos-lite on it, further more you can debug your `Nanos-lite` in `native` mode just like what you did for `klib`.

[yifeifang]

Suggested change

In addition, although it will not cause obvious misunderstandings, after the introduction of Nanos-lite, we will still use the concept of "user process" instead of "user program" in some places. If you can't understand what a process is now, you only need to understand the process as a "running program". Still can’t feel the difference between the two? Let’s give a simple example. If you open Notepad three times, there will be three Notepad processes running on the computer, but there is only one Notepad program on the disk. Process is an important concept in the operating system. Detailed knowledge about processes will be introduced in the operating system class.

In addition, although it will not cause obvious misunderstandings, after the introduction of Nanos-lite, we will still use the concept of "guest process" instead of "guest program" in some places. If you can't understand what a process is now, you only need to understand the process as a "running program". Still can’t feel the difference between the two? Let’s give a simple example. If you open Notepad three times, there will be three Notepad processes running on the computer, but there is only one Notepad program on the disk. Process is an important concept in the operating system. Detailed knowledge about processes will be introduced in the operating system class.

[yifeifang]

Suggested change

	At the beginning, all macros related to the experimental progress in `nanos-lite/include/common.h` are not defined. At this time, the function of Nanos-lite is very simple. Let's briefly sort out the current behavior of Nanos-lite:
	At the beginning, all macros related to the experimental progress in `nanos-lite/include/common.h` are not defined. Currently, the functionality of Nanos-lite is amazingly simple. Let's briefly sort out the current behavior of Nanos-lite:

[yifeifang]

Suggested change

1. Print the logo of Project-N, and output hello information and compilation time through `Log()`. It should be noted that the `Log()` macro defined in Nanos-lite is not the `Log()` macro defined in NEMU . Nanos-lite and NEMU are two independent projects, and their codes will not affect each other. You need to pay attention to this when reading the code. In Nanos-lite, the `Log()` macro outputs through the `printf()` you wrote in `klib`, which will eventually call TRM's `patch()`.

1. Print the logo of Project-N, and output hello information and compilation time through `Log()`. It should be noted that the `Log()` macro defined in Nanos-lite is not the `Log()` macro defined in NEMU . Nanos-lite and NEMU are two independent projects, and their codes will not affect each other. You need to pay attention to this when reading the code. In Nanos-lite, the `Log()` macro write to console through the `printf()` you wrote in `klib`, which will eventually call TRM's `patch()`.

[yifeifang]

Suggested change

	You may not believe it, but the .c and .h files of the framework code undoubtedly contain this ironclad fact, and there is nothing special about even the compilation method. The same is true for GNU/Linux: If you read it If you look at the source code, you will find that GNU/Linux is just a huge C program.
	You may not believe it, but the .c and .h files of the framework code undoubtedly contain this ironclad fact, and there is nothing special about even the compilation method. The same statement holds true for GNU/Linux if you look at the source code, you will find that GNU/Linux is just a huge C program.