From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: VMX ideas Date: Wed, 29 Oct 2008 16:36:48 +0100 Message-ID: <49088310.2090702@redhat.com> References: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: KVM list To: Alexander Graf Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35319 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752621AbYJ2Pgy (ORCPT ); Wed, 29 Oct 2008 11:36:54 -0400 In-Reply-To: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > So I was thinking hard on what to do to circumvent this problem and came > up with several approaches: > 3. Create a root mode bloat framework 4. Enter vmx root mode when the first user opens /dev/kvm and leave it when nobody uses it any more? Also note that there has been some discussion on lkml to move vmx-root on/off out of the kvm module into the kernel. There are a few places where it would be useful for the kernel to handle that without the kvm module being involved, crashdump kexec for example. With that and some locking in place (so only one can use vmx-root at a time) and hypervisors being friendly to each other and grab vmx-root only when they have a guest to run we should be set? cheers, Gerd