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

我写过一篇关于用JavaScript模拟Chip-8系统的文章。

这是一个很好的开始，因为系统不是很复杂，但你仍然了解操作码、堆栈、寄存器等是如何工作的。

我将很快为NES写一篇更长的指南。

共享源设备模拟器包含PocketPC/智能手机模拟器的可构建源代码(需要Visual Studio，在Windows上运行)。我参与了二进制版本的V1和V2。

它解决了许多仿真问题: -从虚拟客户端到物理客户端再到虚拟主机的高效地址转换 - JIT编译客户代码 -模拟周边设备，如网络适配器、触摸屏和音频 - UI集成，主机键盘和鼠标 -保存/恢复状态，用于模拟从低功耗模式恢复

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

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

我从来没有做过像模拟游戏机这样奇特的事情，但我曾经上过一门课程，作业是为Andrew Tanenbaums结构化计算机组织中描述的机器编写模拟器。这很有趣，给了我很多顿悟的时刻。在开始编写一个真正的模拟器之前，您可能需要先阅读一下这本书。

在创建了我自己的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!