From: "Andreas Färber" <afaerber@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QOM-ify QemuConsoles ...
Date: Wed, 20 Mar 2013 14:39:09 +0100 [thread overview]
Message-ID: <5149BBFD.5050300@suse.de> (raw)
In-Reply-To: <51498793.2000209@redhat.com>
Hi Gerd,
Am 20.03.2013 10:55, schrieb Gerd Hoffmann:
> I think the next logical step ahead is to QOM-ify the QemuConsoles, so
> we can link the QemuConsole to the thing actually backing it. For a
> graphical console that would be the emlated graphic device. For a text
> console it would be the serial line or monitor hooked up to it.
>
> With this in place we should be able to answer questions like "which
> device backs this QemuConsole" by inspecting the object tree and handle
> requests like "do a screendump of this device please". It will also be
> useful to setup input routing: "pointer events from $this QemuConsole
> should to $that virtual input device".
>
> Hints how to do that best? Pointers to sample code to look at? From a
> brief look it seems we only QOM-ified emulated devices and not host-side
> objects yet ...
You could look at virtio-rng. TPM doesn't use QOM yet AFAIR.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-03-20 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 9:55 [Qemu-devel] QOM-ify QemuConsoles Gerd Hoffmann
2013-03-20 13:39 ` Andreas Färber [this message]
2013-03-20 14:40 ` Anthony Liguori
2013-03-20 16:00 ` Gerd Hoffmann
2013-03-20 22:51 ` Stefan Berger
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=5149BBFD.5050300@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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).