From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Corey Bryant <coreyb@linux.vnet.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QOM-ify QemuConsoles ...
Date: Wed, 20 Mar 2013 18:51:39 -0400 [thread overview]
Message-ID: <514A3D7B.5010703@linux.vnet.ibm.com> (raw)
In-Reply-To: <5149BBFD.5050300@suse.de>
On 03/20/2013 09:39 AM, Andreas Färber wrote:
> 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.
Yes, I am doing the conversion for TPM.
Stefan
prev parent reply other threads:[~2013-03-20 22:51 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
2013-03-20 14:40 ` Anthony Liguori
2013-03-20 16:00 ` Gerd Hoffmann
2013-03-20 22:51 ` Stefan Berger [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=514A3D7B.5010703@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.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).