From: Eric Blake <eblake@redhat.com>
To: Victor CLEMENT <victor.clement@openwide.fr>, qemu-devel@nongnu.org
Cc: victor.clement@outlook.com, julien.viarddegalbert@openwide.fr
Subject: Re: [Qemu-devel] [PATCH 3/7] chardev: add a scenario engine backend
Date: Fri, 11 Sep 2015 07:11:14 -0600 [thread overview]
Message-ID: <55F2D2F2.1090002@redhat.com> (raw)
In-Reply-To: <1441975830-11828-4-git-send-email-victor.clement@openwide.fr>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On 09/11/2015 06:50 AM, Victor CLEMENT wrote:
> This scenario backend implements the scenario interaction API for all
> character device emulators.
> It provides a callback registration function which registers a chr_write
> callback. It will call the user defined callback on incoming data.
> To write to this character device, qemu_chr_be_write can be used.
>
> Signed-off-by: Victor CLEMENT <victor.clement@openwide.fr>
> ---
> +++ b/qapi-schema.json
> @@ -3042,7 +3042,8 @@
> 'vc' : 'ChardevVC',
> 'ringbuf': 'ChardevRingbuf',
> # next one is just for compatibility
> - 'memory' : 'ChardevRingbuf' } }
> + 'memory' : 'ChardevRingbuf',
> + 'scenario': 'ChardevDummy' } }
Missing documentation of the new union branch, including mention that it
was added in 2.5.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-09-11 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 12:50 [Qemu-devel] [PATCH 0/7] Qemu scenario engine Victor CLEMENT
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 [this message]
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=55F2D2F2.1090002@redhat.com \
--to=eblake@redhat.com \
--cc=julien.viarddegalbert@openwide.fr \
--cc=qemu-devel@nongnu.org \
--cc=victor.clement@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.