From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NcME9-0000GF-PY
	for qemu-devel@nongnu.org; Tue, 02 Feb 2010 12:07:49 -0500
Received: from [199.232.76.173] (port=47516 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NcME9-0000Fv-DU
	for qemu-devel@nongnu.org; Tue, 02 Feb 2010 12:07:49 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <chrisw@redhat.com>) id 1NcMDs-00038W-MF
	for qemu-devel@nongnu.org; Tue, 02 Feb 2010 12:07:49 -0500
Received: from mx1.redhat.com ([209.132.183.28]:65127)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <chrisw@redhat.com>) id 1NcMDr-00037u-OD
	for qemu-devel@nongnu.org; Tue, 02 Feb 2010 12:07:32 -0500
Date: Tue, 2 Feb 2010 09:07:26 -0800
From: Chris Wright <chrisw@redhat.com>
Message-ID: <20100202170726.GC20233@x200.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] KVM developer call minutes (Feb 2)
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org

Minutes (please reply w/ corrections or follow-ups):

state of in-kernel APIC/IOAPIC/PIT upstream merge
- Glauber?...

road map to get rid of qemu-kvm's slot management (IMHO: qemu-kvm-0.13)
- no real feedback here

- any further ongoing/planned upstream merge efforts?
  - SMP
    - needs in-kernel irqchip support upstream
    - possibly make it a stream in uq for integration and autotesting
  - PCI Device Assignment cleanup, proper capabilities support
    - do we move to uio support before pushing upstream?
    - Michael's UIO patch for 2.3 devices is upstream, so moving to uio
      would add a feature
    - what is missing w/out PCIe bus emulation
      - AER, ARI, few other less critical things
    - any 64-bit issues or other things that a driver may probe for that
      will break ww/out PCIe
      - most are probing PCI capabilities

upstream queue uq qemu-kvm 
- flush mmio buffer periodically
- enabled unconditional save/restore
- started porting -mempath
- getting autotest to run on upstream to autotest before sending patches
  to upstream
- anthony wants to receive pull request w/ inline patches for review

qmp feature negotiation issue
- Luiz and Markus discussing alternatives, either seems fine
  - Anthony will follow-up on list