[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4912C75B.8050508@redhat.com>
Date: Thu, 06 Nov 2008 12:30:51 +0200
From: Avi Kivity <avi@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: Eduardo Habkost <ehabkost@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Simon Horman <horms@...ge.net.au>,
Andrew Morton <akpm@...l.org>, Vivek Goyal <vgoyal@...hat.com>,
Haren Myneni <hbabu@...ibm.com>,
Andrey Borzenkov <arvidjaar@...l.ru>, mingo@...hat.com,
"Rafael J. Wysocki" <rjw@...k.pl>, kexec@...ts.infradead.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/16] x86: Emergency virtualization disable function
Eric W. Biederman wrote:
>
>> 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?
>
There is a de-facto convention supported by at least vmware and kvm. If
cr4.vmxe is 1, then we are in vmx operation. If cr4.vmxe is 0, then we
are not in vmx operation. This allows us to determine whether we need
to execute vmxoff without any APIs.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists