一个框架、两个界面Aframeworkforthetwo.docVIP

一个框架、两个界面 A framework for the two interfaces 是Linux兼容内核开发的主体 Linux kernel development is compatible with the main 毛德操 Maud operation 我们开发 Linux 兼容内核的目标是让 Windows 应用软件可以直接在这个内核上运行，更确切地说是在以这个内核为核心的操作系统上运行。 We develop Linux-compatible core goal is to make Windows applications can run in the kernel, and more specifically to the kernel in the core operating systems. 同时，还要让为 Windows 而开发的一些设备驱动模块也能装入这个内核运行。 At the same time, but also to some developed for the Windows device driver module into the kernel can run. 这一方面是因为针对 Windows 开发的设备驱动模块在数量和品种上都远远多于 Linux ；另一方面是因为有愈来愈多的应用软件需要跟专用的设备驱动模块配套运行，缺了这设备驱动模块就运行不起来。 This is because the development of device drivers for Windows modules, both in number and variety of far more than Linux;the other hand, because there are more and more application needs with a dedicated device driver modules supporting the operation, lack of this device driver modules to run it up. 只有同时实现了这两个目标，才能说 Linux 的内核兼容了 Windows 内核。 Only while achieving these two objectives, to say that Linux kernel compatible with the Windows kernel. 那么，为了要达到这两个目标，我们必须对 Linux 内核作些什么修改和扩充呢？ So, in order to achieve these two objectives, we must modify the Linux kernel and expansion of what made it? 本文就是要对此作一分析，并回答这个问题。 This article is an analysis to this and to answer this question. 首先，一段封闭的程序、如果既不调用库程序、也不作系统调用，是跟操作系统无关的，只要所在机器的 CPU 跟这段程序编译时的目标 CPU 相符就可以了。 First, a closed procedure, if not call the library program, not as system calls, is not related with the operating system, as long as the machine where the CPU with the goal of this program compiled CPU line on it. 这是因为，以 PC 机为例，这段程序编译后所生成的所有指令全都是 x86 机器指令，而且所有这些指令全都可以正常运行，它的所有跳转指令和子程序调用指令的目标都不会越出这段程序的边界。 This is because the PC, for example, generated by this program compiled all the instructions are all x86 machine instructions, and all of these instructions can all function properly, its all jump instructions and subroutine call instructions are not the target beyond the boundaries of this program. 其次，即使需要调用库程序，只要不直接或间接进行