aboutsummaryrefslogtreecommitdiff
path: root/qemu-doc.texi
diff options
context:
space:
mode:
authorAnthony Liguori <aliguori@us.ibm.com>2012-03-28 15:42:02 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2012-03-30 08:14:11 -0500
commitc7f0f3b1c826901358a0656f80a5fabb88f73c61 (patch)
treec1ff5a6ed93543dd2580e11397d21ee190e3fd23 /qemu-doc.texi
parentb93b63f574ccb451e82f81c6da7c39b3ecb4f24c (diff)
downloadqemu-c7f0f3b1c826901358a0656f80a5fabb88f73c61.zip
qemu-c7f0f3b1c826901358a0656f80a5fabb88f73c61.tar.gz
qemu-c7f0f3b1c826901358a0656f80a5fabb88f73c61.tar.bz2
qtest: add test framework
The idea behind qtest is pretty simple. Instead of executing a CPU via TCG or KVM, rely on an external process to send events to the device model that the CPU would normally generate. qtest presents itself as an accelerator. In addition, a new option is added to establish a qtest server (-qtest) that takes a character device. This is what allows the external process to send CPU events to the device model. qtest uses a simple line based protocol to send the events. Documentation of that protocol is in qtest.c. I considered reusing the monitor for this job. Adding interrupts would be a bit difficult. In addition, logging would also be difficult. qtest has extensive logging support. All protocol commands are logged with time stamps using a new command line option (-qtest-log). Logging is important since ultimately, this is a feature for debugging. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'qemu-doc.texi')
0 files changed, 0 insertions, 0 deletions