Lenshood

Based on disk and file management, now we are able to store the user space program on the disk, and let them run after kernel started. But before that, there is still a topic we haven't covered: how does xv6 jump from kernel space to user space?

After all, the content we talked about in previous chapters is only limited in the supervisor level, even machine level, where the code has full control of hardware. However, the user space program cannot be granted such huge scope of control, then we should know how to jump from kernel space to user space, so that we could provide a safer environment for the user program.

In this chapter, we are going to find it out.

With all of the content in the previous chapters, we have known how to initialize and run a process, but before the kernel runs the first line of a process's code, a question still remained, how does my user program store in the disk and how is it loaded?

In this chapter, we are going to discover the disk management and file system in the xv6, we'll see the persistence stack from the top to the bottom, let's get started!

In this chapter, we are going to explore the cpu virtualization, also known as process, in the xv6.

I'm really excited about writing this chapter, because process is one of the fundamental concepts of the operating system. Process is very useful for multiple tasks, and in the design wise, its abstraction is also very elegant.

We have learnt how to setup risc-v in rust, and also initialized risc-v to be able to print format strings, in this chapter we are taking the first look of the OS kernel, and will try to figure out the memory management in xv6.

With the foundation established in the previous article, we now have a working Rust environment on RISC-V.

In this second installment, we'll examine the actual xv6 code, handling the initialization from machine level to supervisor level, and ultimately implementing the printf!() macro.

Xv6 is one of the best operating systems for teaching. It’s a great way to learn about how an OS works with basic functions and few line of code.

Originally, xv6 was written in C, which is awesome for students to get hands-on experience with such a classic programming language. But now that Rust is gaining traction—especially since rust-for-linux is becoming a part of the main line Linux—wouldn’t it be fun to run xv6 using Rust?

As a perfect way to kill time, I have migrated most of xv6 from C to Rust. You can check it out here. During this migration process, I encountered many sorts of issues and tricky stuff, nothing brings me more satisfaction than successfully resolving a problem!

Therefore, I believe it would be cool for me to share my experiences through a series of articles detailing how I did this, complete with a more structured approach and clear procedures.

All right, let's get started...

本文翻译自 Gregor Resing（IBM）的文章 The Software Defined Vehicle。

当今的汽车与数年前的汽车相比，虽然作为载具的主要目的变化不大，但不论是在驾乘体验、智能化水平还是交互方式上，都发生了质的飞跃。

为了能支撑新一代汽车所提供的这种智能化服务水平，显而易见，需要将软件平台与硬件平台相互分离和抽象以提升灵活性，这种被称为软件定义汽车（Software Defined Vehicle，下文简称 SDV）的设计方法基于更加灵活和易于扩展的软件作为汽车的核心，将传统的汽车升级为拥有诸如智能驾驶、深度娱乐、个性化人机交互能力的 “第三空间”。

SDV 带来了一系列汽车设计的革命性跨越，同时也引入了各种新的困难。诸如性能、可靠性、安全性、易用性等在软件领域长期存在的跨领域、跨业务型挑战，随着 SDV 被一并引入了汽车领域。

本文是对论文 LEARNING PERFORMANCE-IMPROVING CODE EDITS 的翻译

随着智能汽车的不断发展，智能座舱在性能与可靠性上暴露出体验不佳，投诉渐多的问题，本文从工程化方法的角度简述了如何构建智能座舱软件的评估框架，以及如何持续改进性能和可靠性。