From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit shah <amit.shah@redhat.com>,
hdegoede@redhat.com, aliguori@us.ibm.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/5] for spice post load char device hook
Date: Wed, 20 Mar 2013 05:56:01 -0400 (EDT) [thread overview]
Message-ID: <2064240700.11477136.1363773361296.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1363772908-30870-1-git-send-email-alevy@redhat.com>
Please ignore this email, sent before I remembered to squash one of the patches.
> This reworks my former patch
> (http://patchwork.ozlabs.org/patch/227678/ - sorry
> Hans, can't find the version you posted) per Gerd's suggestion.
> Specifically it
> adds a new qemu_chr_fe_post_load api that is called by the front end
> and
> implemented by the backend. virtio-console implements it, adding it's
> own hook
> which is called by virtio-serial-bus upon post_load from the timer,
> so that
> qemu_chr_fe_post_load is called when the vm is already in the running
> state.
> This makes the spice-qemu-char usage very simple by not requiring yet
> another
> timer.
>
> Alon Levy (5):
> char: add a post_load callback
> merge to char.h
> virtio-serial: add a post_load callback implemented by port
> virtio-console: implement post_load to call to
> qemu_chr_fe_post_load
> spice-qemu-char: register interface on post load
>
> hw/virtio-console.c | 11 +++++++++++
> hw/virtio-serial-bus.c | 5 +++++
> hw/virtio-serial.h | 2 ++
> include/char/char.h | 9 +++++++++
> qemu-char.c | 7 +++++++
> spice-qemu-char.c | 9 +++++++++
> 6 files changed, 43 insertions(+)
>
> --
> 1.8.1.4
>
>
>
prev parent reply other threads:[~2013-03-20 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 9:48 [Qemu-devel] [PATCH 0/5] for spice post load char device hook Alon Levy
2013-03-20 9:56 ` Alon Levy [this message]
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=2064240700.11477136.1363773361296.JavaMail.root@redhat.com \
--to=alevy@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=hdegoede@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).