From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47962)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1WFmEm-0004Sz-O7
	for qemu-devel@nongnu.org; Tue, 18 Feb 2014 10:05:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1WFmEf-0001Q8-R5
	for qemu-devel@nongnu.org; Tue, 18 Feb 2014 10:05:32 -0500
Received: from mx1.redhat.com ([209.132.183.28]:12132)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <quintela@redhat.com>) id 1WFmEf-0001Pw-K8
	for qemu-devel@nongnu.org; Tue, 18 Feb 2014 10:05:25 -0500
From: Juan Quintela <quintela@redhat.com>
Date: Tue, 18 Feb 2014 16:05:22 +0100
Message-ID: <87d2ikcvgt.fsf@elfo.mitica>
MIME-Version: 1.0
Content-Type: text/plain
Subject: [Qemu-devel] KVM call minutes for 2014-02-18
Reply-To: quintela@redhat.com
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: KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel qemu-devel <qemu-devel@nongnu.org>



2014-02-18
----------

* x2apic?

-  Pending patch for cpu feature flag.
-  Should this be the default.
-  It is not for 32bits, but should it be for 64bit?
-  libvirt always use x2apic, unconditionally?
-  What happens if one side of migration uses -m <cpu_something and the
   other -m cpu_something+x2apic
-  disabling if for all old machine types
-  Use the same that hyperv flags?


* release
- No Anthony
- People happy (on happy enough) with current schedule

* Maintenance?
- How is being handling patches for the stable release?
  CC: stable@  for stable maintance.
- add documentation about what/how to send patches for stable release
- Regressions deserve a backport almost always?
- There is no stable tree public where we see what patches are being integrated?
- How can we make more people additoally to Michael to work with stable branches
- Should we change anynthing?