From: Victor CLEMENT <victor.clement@openwide.fr>
To: qemu-devel@nongnu.org
Cc: victor.clement@outlook.com,
Victor CLEMENT <victor.clement@openwide.fr>,
julien.viarddegalbert@openwide.fr
Subject: [Qemu-devel] [PATCH 0/7] Qemu scenario engine
Date: Fri, 11 Sep 2015 14:50:23 +0200 [thread overview]
Message-ID: <1441975830-11828-1-git-send-email-victor.clement@openwide.fr> (raw)
This patch introduce a testing component for Qemu guest OS: the scenario
engine.
The Qemu scenario engine is a framework designed to test the software running
on the guest machine. It allows interacting with the guest virtual devices by
stimulating inputs and reading outputs from outside of the virtual machine.
It also provides an utility to schedule precise time based events to run
through a "test scenario".
As it is a whole subsystem, a github repository providing a complete
documentation and a demonstration is available at the following address:
https://github.com/Openwide-Ingenierie/qemu-scenario-engine-demo
Victor CLEMENT (7):
configure: add --enable-scenario-engine option
gpio-pl061: add a scenario engine interaction API
chardev: add a scenario engine backend
scenario-engine: add utilities
scenario-engine: add a time based event scheduler
scenario engine: provide a scenario file template
scenario engine: add a Qemu option to start it
Makefile.objs | 8 ++
backends/Makefile.objs | 1 +
backends/scenario.c | 107 +++++++++++++++++++++++++
configure | 8 ++
hw/gpio/pl061.c | 38 +++++++++
include/hw/gpio/pl061_simu.h | 20 +++++
include/scenario/scenario.h | 5 ++
include/scenario/scheduler.h | 26 ++++++
include/scenario/utils.h | 23 ++++++
include/sysemu/char.h | 13 +++
qapi-schema.json | 3 +-
qemu-char.c | 5 ++
qemu-options.hx | 12 +++
scenario/scenario.c | 168 ++++++++++++++++++++++++++++++++++++++
scenario/scheduler.c | 186 +++++++++++++++++++++++++++++++++++++++++++
scenario/utils.c | 65 +++++++++++++++
vl.c | 45 ++++++++++-
17 files changed, 731 insertions(+), 2 deletions(-)
create mode 100644 backends/scenario.c
create mode 100644 include/hw/gpio/pl061_simu.h
create mode 100644 include/scenario/scenario.h
create mode 100644 include/scenario/scheduler.h
create mode 100644 include/scenario/utils.h
create mode 100644 scenario/scenario.c
create mode 100644 scenario/scheduler.c
create mode 100644 scenario/utils.c
--
2.5.1
next reply other threads:[~2015-09-11 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 12:50 Victor CLEMENT [this message]
2015-09-11 12:50 ` [Qemu-devel] [PATCH 1/7] configure: add --enable-scenario-engine option Victor CLEMENT
2015-09-11 12:50 ` [Qemu-devel] [PATCH 2/7] gpio-pl061: add a scenario engine interaction API Victor CLEMENT
2015-09-11 12:50 ` [Qemu-devel] [PATCH 3/7] chardev: add a scenario engine backend Victor CLEMENT
2015-09-11 13:11 ` Eric Blake
2015-09-11 12:50 ` [Qemu-devel] [PATCH 4/7] scenario-engine: add utilities Victor CLEMENT
2015-09-11 12:50 ` [Qemu-devel] [PATCH 5/7] scenario-engine: add a time based event scheduler Victor CLEMENT
2015-09-11 12:50 ` [Qemu-devel] [PATCH 6/7] scenario engine: provide a scenario file template Victor CLEMENT
2015-09-11 12:50 ` [Qemu-devel] [PATCH 7/7] scenario engine: add a Qemu option to start it Victor CLEMENT
2015-09-11 13:11 ` [Qemu-devel] [PATCH 0/7] Qemu scenario engine Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1441975830-11828-1-git-send-email-victor.clement@openwide.fr \
--to=victor.clement@openwide.fr \
--cc=julien.viarddegalbert@openwide.fr \
--cc=qemu-devel@nongnu.org \
--cc=victor.clement@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).