c7f0f3b1c8
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>
36 lines
557 B
C
36 lines
557 B
C
/*
|
|
* Test Server
|
|
*
|
|
* Copyright IBM, Corp. 2011
|
|
*
|
|
* Authors:
|
|
* Anthony Liguori <aliguori@us.ibm.com>
|
|
*
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
* See the COPYING file in the top-level directory.
|
|
*
|
|
*/
|
|
|
|
#ifndef QTEST_H
|
|
#define QTEST_H
|
|
|
|
#include "qemu-common.h"
|
|
|
|
extern int qtest_allowed;
|
|
extern const char *qtest_chrdev;
|
|
extern const char *qtest_log;
|
|
|
|
static inline bool qtest_enabled(void)
|
|
{
|
|
return qtest_allowed;
|
|
}
|
|
|
|
static inline int qtest_available(void)
|
|
{
|
|
return 1;
|
|
}
|
|
|
|
int qtest_init(void);
|
|
|
|
#endif
|