From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50390) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WG8bX-0001wx-U2 for qemu-devel@nongnu.org; Wed, 19 Feb 2014 09:58:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WG8bP-0005OJ-By for qemu-devel@nongnu.org; Wed, 19 Feb 2014 09:58:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:59053) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WG8bP-0005O8-4C for qemu-devel@nongnu.org; Wed, 19 Feb 2014 09:58:23 -0500 From: Eduardo Habkost Date: Wed, 19 Feb 2014 11:58:09 -0300 Message-Id: <1392821892-26682-1-git-send-email-ehabkost@redhat.com> Subject: [Qemu-devel] [PATCH 0/3] Enable x2apic by default on KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, =?UTF-8?q?Andreas=20F=C3=A4rber?= Cc: Peter Maydell , "Michael S. Tsirkin" , Bandan Das , Anthony Liguori , Igor Mammedov , Paolo Bonzini , Richard Henderson This is the approach I believe was agreed upon during the last QEMU developers conf call (sorry I didn't join, the meeting timezone change confused me). Some may notice that representing this new behavior using solely default values on CPU properties may be a little difficult. Making it possible to replace x86_cpu_compat_disable_kvm_features() with compat_props entries may be an interesting problem, too. Eduardo Habkost (3): target-i386: Make kvm_default_features an array target-i386: Introduce x86_cpu_compat_disable_kvm_features() target-i386: Enable x2apic by default on KVM hw/i386/pc_piix.c | 7 ++++--- hw/i386/pc_q35.c | 2 ++ target-i386/cpu.c | 20 +++++++++++++++----- target-i386/cpu.h | 4 ++-- 4 files changed, 23 insertions(+), 10 deletions(-) -- 1.8.5.3