From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:50972)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1TLaHI-0007DL-Va
	for qemu-devel@nongnu.org; Tue, 09 Oct 2012 09:55:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1TLaHD-0005qi-UY
	for qemu-devel@nongnu.org; Tue, 09 Oct 2012 09:55:20 -0400
Received: from greensocs.com ([87.106.252.221]:34838
	helo=s15328186.onlinehome-server.info)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fred.konrad@greensocs.com>) id 1TLaHD-0005pq-Nl
	for qemu-devel@nongnu.org; Tue, 09 Oct 2012 09:55:15 -0400
Message-ID: <50742CBC.50804@greensocs.com>
Date: Tue, 09 Oct 2012 15:55:08 +0200
From: =?ISO-8859-1?Q?KONRAD_Fr=E9d=E9ric?= <fred.konrad@greensocs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Virtio devices with mmio.
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: qemu-devel@nongnu.org, pbonzini@redhat.com, aliguori@us.ibm.com, Mark Burton <mark.burton@greensocs.com>

Hi,

We are actually trying to use virtio devices with Virt-mmio bus.

The idea is to use theses patches I mentioned in a previous mail 
(http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg04913.html).

We are currently drawing the plan of how we can complete theses patches 
to have it upstreamed.

Actually we have two major topics.

Backends / transport separation :

We need a good separation between backends and virtio-pci/virtio-mmio, 
actually it seems to be the case for virt-mmio but not for virtio-pci as 
the old device file is temporary kept for compability ( virtio-pci-new.c ).

Quality of code :

We need to be sure that all the devices are happy with the QOM design, 
any hints about that ?

For the moment your plan is :

Implementing virtio-xxx-pci which create virtio-pci and virtio-xxx ( as 
suggested by Evgeny Voevodin ).
Looking at the command line issues.
Refactor remaining back-ends ( virtio-scsi, virto-serial, ... ) and 
update s390.
Check the QOM design of all the modification ( virtio-mmio, transport, 
... ).

Is that making sense ? Any suggestion ?

I'll reporting back by the end of the week.

Fred