|
|
|
| Authored by: Anonymous on Wednesday, May 30 2012 @ 10:20 PM EDT |
Isn't it more of
Java VM - a virtualized Java machine
Dalvik VM - a virtualized Dalvik machine
Python Interpreter - interprets Python code
Small talk Interpreter - interprets Small talk code
Java compiler - takes Java code and translates to Java machine instructions
C++ compiler - takes C++ code and translates it to the targeted machine
instructions
Game console emulator - makes the user think it is the game console by
virtualizing it and making the wall clock time of both be the same[ Reply to This | Parent | # ]
|
- hmm.. - Authored by: Anonymous on Wednesday, May 30 2012 @ 10:46 PM EDT
- hmm.. Simulators... - Authored by: Anonymous on Wednesday, May 30 2012 @ 11:07 PM EDT
- Virtuoso - Authored by: Anonymous on Wednesday, May 30 2012 @ 11:11 PM EDT
| |
| Authored by: Anonymous on Wednesday, May 30 2012 @ 10:25 PM EDT |
Oh, moons and moons past.
I used emulators for hardware that hadn't been built yet.
So the code written in the emulator rig could perform all
the functions of the hardware once that one eventually gets
built. That could include using opcodes that had, at the
time, no silicon-only equivalent but only silicon-and-
temporaryware.
And the first use I remember of, for the term "Virtual
Machine", was by IBM for the CP/CMS that ran on the S/360
model 67. CP/CMS ("Control Program/Common (?) Management
System") was indeed executing directly the S/360 instruction
set - but as it was running in non-privileged mode it would
trap on things like I/O or non-existent opcodes, giving
control to CMS.
I think IBM also crafted the term "Hypervisor" when the
S/370 made VM/370 more commonplace and you could actually
run e.g. OS/MVS either in virtual mode (under control of
CMS) or on the bare metal.
So:
* Emulation is trying to imitate something, in this case a
different piece of silicon than what you actually have.
Like running Android in emulation mode on a PC: The emulated
Android "runs" ARM opcodes, but these are
imitated/emulated/simulated using Intel opcodes on the PC.
* Virtualization: Makes one believe (s)he has several pieces
of iron at his/her disposal, while there is only one, the
other are ghosts - but they all share a similar setup.
The boundaries are getting fuzzier with time, and what would
you call the result of emulating a network of Androids on a
PC ?
Just my $0.02.
Bck not logged in[ Reply to This | Parent | # ]
|
|
|
|
|
