From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: VMX ideas Date: Sun, 02 Nov 2008 12:28:05 +0200 Message-ID: <490D80B5.9090306@redhat.com> References: <687FC948-DBF4-4A7C-AD14-F6DB53A092D6@suse.de> <49088310.2090702@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Graf , KVM list To: Gerd Hoffmann Return-path: Received: from mx2.redhat.com ([66.187.237.31]:47706 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753307AbYKBK2L (ORCPT ); Sun, 2 Nov 2008 05:28:11 -0500 In-Reply-To: <49088310.2090702@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Gerd Hoffmann wrote: >> 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 That means that although kvm is loaded it may be unable to service /dev/kvm... something I'd like to avoid. -- error compiling committee.c: too many arguments to function