From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Graf <agraf@suse.de>
Subject: Re: KVM call minutes 2013-01-29
Date: Tue, 29 Jan 2013 21:53:49 +0100
Message-ID: <510836DD.3010707@suse.de>
References: <871ud4gfoa.fsf@elfo.elfo>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	=?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>,
	Anthony Liguori <aliguori@us.ibm.com>
To: quintela@redhat.com
Return-path: <kvm-owner@vger.kernel.org>
Received: from cantor2.suse.de ([195.135.220.15]:45507 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751033Ab3A2Ux7 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 29 Jan 2013 15:53:59 -0500
In-Reply-To: <871ud4gfoa.fsf@elfo.elfo>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 01/29/2013 04:41 PM, Juan Quintela wrote:
> * Buildbot: discussed on the list (Andreas retired it)
>
> * Replacing select(2) so that we will not hit the 1024 fd_set limit in the
>    future. (stefan)
>
>    Add checks for fd's bigger than 1024? multifunction devices uses lot
>    of fd's for device.
>
>    Portability?
>    Use glib?  and let it use poll underneath.
>    slirp is a problem.
>    in the end loop: moving to a glib event loop, how we arrive there is the discussion.
>
>
> * Outstanding virtio work for 1.4
>    - Multiqueue virtio-net (Amos/Michael)
>      version appeared today, problably it is on mergeable state
>    - Refactorings (Fred/Peter)
>      unlike before the hard freeze
>    - virtio-ccw (Cornelia/Alex)
>      conflict with multiqueue problably (alex)
>      shouldn't (famous last words)
>    - Do virtio-ccw used old style virtio API, and make integrating the
>      refactorings more difficult?
>    - Pushing refactorings to 1.5
>
> * What's the plan for -device and IRQ assignment? (Alex)
>
>    Alex will fill this

When using -device, we can not specify an IRQ line to attach to the 
device. This works for some special buses like PCI, but not in the 
generic case. We need it generically for virtio-mmio and for potential 
platform assigned vfio devices though.

The conclusion we came up with was that in order to model IRQ lines 
between arbitrary devices, we should use QOM and the QOM name space. 
Details are up for Anthony to fill in :).


Alex