From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tr8kV-0003yw-Jk for qemu-devel@nongnu.org; Fri, 04 Jan 2013 09:59:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tr8kU-0002T6-4f for qemu-devel@nongnu.org; Fri, 04 Jan 2013 09:59:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44859) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tr8kT-0002RA-Tj for qemu-devel@nongnu.org; Fri, 04 Jan 2013 09:59:54 -0500 From: Eduardo Habkost Date: Fri, 4 Jan 2013 12:52:23 -0200 Message-Id: <1357311145-16410-1-git-send-email-ehabkost@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] Disable kvm_mmu_op by default on pc-1.4 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kvm@vger.kernel.org, Gleb Natapov , "Michael S. Tsirkin" , Marcelo Tosatti , Igor Mammedov , =?UTF-8?q?Andreas=20F=C3=A4rber?= The kvm_mmu_op feature was removed from the kernel since v3.3 (released in March 2012), it was marked for removal since January 2011 and it's slower than shadow or hardware assisted paging (see kernel commit fb92045843). It doesn't make sense to keep it enabled by default. Also, keeping it enabled by default would cause unnecessary hassle when libvirt start using the "enforce" option. Eduardo Habkost (2): target-i386: don't set any KVM flag by default if KVM is disabled target-i386: disable kvm_mmu_op by default on pc-1.4 hw/pc_piix.c | 11 ++++++++++- target-i386/cpu.c | 15 ++++++++++++--- target-i386/cpu.h | 1 + 3 files changed, 23 insertions(+), 4 deletions(-) -- 1.7.11.7