From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:41365)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanb@linux.vnet.ibm.com>) id 1UIRrF-0000w5-RE
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 18:51:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanb@linux.vnet.ibm.com>) id 1UIRrE-00038j-GQ
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 18:51:45 -0400
Received: from e7.ny.us.ibm.com ([32.97.182.137]:57265)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanb@linux.vnet.ibm.com>) id 1UIRrE-00037p-Ca
	for qemu-devel@nongnu.org; Wed, 20 Mar 2013 18:51:44 -0400
Received: from /spool/local
	by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only!
	Violators will be prosecuted
	for <qemu-devel@nongnu.org> from <stefanb@linux.vnet.ibm.com>;
	Wed, 20 Mar 2013 18:51:42 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236])
	by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 143076E8047
	for <qemu-devel@nongnu.org>; Wed, 20 Mar 2013 18:51:38 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217])
	by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id
	r2KMpeKZ283434
	for <qemu-devel@nongnu.org>; Wed, 20 Mar 2013 18:51:40 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1])
	by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id
	r2KMpdue007498
	for <qemu-devel@nongnu.org>; Wed, 20 Mar 2013 19:51:40 -0300
Message-ID: <514A3D7B.5010703@linux.vnet.ibm.com>
Date: Wed, 20 Mar 2013 18:51:39 -0400
From: Stefan Berger <stefanb@linux.vnet.ibm.com>
MIME-Version: 1.0
References: <51498793.2000209@redhat.com> <5149BBFD.5050300@suse.de>
In-Reply-To: <5149BBFD.5050300@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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: =?ISO-8859-1?Q?Andreas_F=E4rber?= <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>

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