是的，你必须“手工”解释整个二进制机器码的混乱。不仅如此，大多数情况下，您还必须模拟一些在目标机器上没有等效硬件的外来硬件。

简单的方法是一个接一个地解释指令。这工作得很好，但是很慢。一种更快的方法是重新编译——将源机器码转换为目标机器码。这比较复杂，因为大多数指令都不是一对一映射的。相反，您将不得不制定涉及额外代码的详细变通方案。但最终还是要快得多。大多数现代模拟器都是这样做的。

在创建了我自己的80年代BBC微型计算机模拟器(类型VBeeb到谷歌)后，有许多事情要知道。

You're not emulating the real thing as such, that would be a replica. Instead, you're emulating State. A good example is a calculator, the real thing has buttons, screen, case etc. But to emulate a calculator you only need to emulate whether buttons are up or down, which segments of LCD are on, etc. Basically, a set of numbers representing all the possible combinations of things that can change in a calculator. You only need the interface of the emulator to appear and behave like the real thing. The more convincing this is the closer the emulation is. What goes on behind the scenes can be anything you like. But, for ease of writing an emulator, there is a mental mapping that happens between the real system, i.e. chips, displays, keyboards, circuit boards, and the abstract computer code. To emulate a computer system, it's easiest to break it up into smaller chunks and emulate those chunks individually. Then string the whole lot together for the finished product. Much like a set of black boxes with inputs and outputs, which lends itself beautifully to object oriented programming. You can further subdivide these chunks to make life easier.

Practically speaking, you're generally looking to write for speed and fidelity of emulation. This is because software on the target system will (may) run more slowly than the original hardware on the source system. That may constrain the choice of programming language, compilers, target system etc. Further to that you have to circumscribe what you're prepared to emulate, for example its not necessary to emulate the voltage state of transistors in a microprocessor, but its probably necessary to emulate the state of the register set of the microprocessor. Generally speaking the smaller the level of detail of emulation, the more fidelity you'll get to the original system. Finally, information for older systems may be incomplete or non-existent. So getting hold of original equipment is essential, or at least prising apart another good emulator that someone else has written!

当你开发一个模拟器时，你是在解释系统正在运行的处理器组件(Z80、8080、PS CPU等)。

您还需要模拟系统拥有的所有外设(视频输出、控制器)。

你应该开始为简单的系统编写模拟器，比如旧的Game Boy(使用Z80处理器，我是不是没有弄错)或C64。

还可以查看Darek Mihocka的Emulators.com，获得关于jit指令级优化的建议，以及许多关于构建高效模拟器的其他好东西。

添加@Cody Brocious提供的答案 在虚拟化环境中，您正在向虚拟机模拟一个新系统(CPU、I/O等)，我们可以看到以下类别的模拟器。

解释:bochs是解释器的一个例子，它是一个x86 PC模拟器，它把来自客户系统的每条指令翻译成另一组指令(主机ISA的指令)来产生预期的效果。是的，它非常慢，它不缓存任何东西，所以每条指令都经过相同的周期。

动态仿真器:Qemu是一个动态仿真器。它可以实时翻译客户指令，也可以缓存结果。最好的部分是直接在主机系统上执行尽可能多的指令，这样模拟就更快了。正如Cody所提到的，它将代码划分为块(一个单独的执行流)。

静态模拟器:据我所知，没有静态模拟器可以帮助虚拟化。

模拟可能看起来令人生畏，但实际上比模拟容易得多。

任何处理器通常都有一个编写良好的描述状态、交互等的规范。

如果您根本不关心性能，那么您可以使用非常优雅的面向对象程序轻松地模拟大多数老式处理器。例如，X86处理器需要一些东西来维护寄存器的状态(简单)，需要一些东西来维护内存的状态(简单)，还需要一些东西来接收每个传入的命令并将其应用到机器的当前状态。如果您真的需要准确性，您还可以模拟内存转换、缓存等，但这是可行的。

In fact, many microchip and CPU manufacturers test programs against an emulator of the chip and then against the chip itself, which helps them find out if there are issues in the specifications of the chip, or in the actual implementation of the chip in hardware. For example, it is possible to write a chip specification that would result in deadlocks, and when a deadline occurs in the hardware it's important to see if it could be reproduced in the specification since that indicates a greater problem than something in the chip implementation.

当然，电子游戏的模拟器通常关心性能，所以它们不会使用简单的实现，它们还包括与主机系统的操作系统接口的代码，例如使用绘图和声音。

考虑到老式电子游戏(NES/SNES等)非常缓慢的性能，在现代系统上进行仿真相当容易。事实上，更令人惊讶的是，你可以下载一套SNES游戏或Atari 2600游戏，考虑到当这些系统流行时，免费访问每个卡带都是一个梦想。