From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 08/16] x86: Emergency virtualization disable function Date: Thu, 06 Nov 2008 02:22:39 -0800 Message-ID: References: <1225810364-8990-1-git-send-email-ehabkost@redhat.com> <1225810364-8990-9-git-send-email-ehabkost@redhat.com> <20081105175235.GJ5247@blackpad> <4912BD67.8000704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Eduardo Habkost , Ingo Molnar , Simon Horman , Andrew Morton , Vivek Goyal , Haren Myneni , Andrey Borzenkov , mingo@redhat.com, "Rafael J. Wysocki" , kexec@lists.infradead.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Avi Kivity Return-path: Received: from out02.mta.xmission.com ([166.70.13.232]:56447 "EHLO out02.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753408AbYKFKZY (ORCPT ); Thu, 6 Nov 2008 05:25:24 -0500 In-Reply-To: <4912BD67.8000704@redhat.com> (Avi Kivity's message of "Thu, 06 Nov 2008 11:48:23 +0200") Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity writes: > Eduardo Habkost wrote: >> We could move the set_virt_disable_func() calls to vmx.c and svm.c (on >> hardware_setup/hardware_unsetup). One could argue that it is sort of a >> coincidence that we need the code for both vmx and svm. >> > > I don't share this fear of function calls, but perhaps that's due to lack of > experience with kdump. Mostly I'm just afraid of extra complexity. > If you want to be extra simple and safe, remove kvm from the equation. Make the > disabling code part of kdump/emergency_restart and only rely on the convention > that cr3.vmxe == vmxon. Convention? > That has the advantage of working with other virtualization systems as well. Sounds good. Eric