From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:47208)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UIJFD-00022L-N6
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 09:39:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UIJFC-0005lI-7V
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 09:39:55 -0400
Received: from cantor2.suse.de ([195.135.220.15]:35930 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UIJFC-0005KN-1S
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 09:39:54 -0400
Message-ID: <5149BBFD.5050300@suse.de>
Date: Wed, 20 Mar 2013 14:39:09 +0100
From: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <51498793.2000209@redhat.com>
In-Reply-To: <51498793.2000209@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] QOM-ify QemuConsoles ...
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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.
>=20
> 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".
>=20
> 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-sid=
e
> objects yet ...

You could look at virtio-rng. TPM doesn't use QOM yet AFAIR.

Cheers,
Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg