From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] Activate Virtualization On Demand
Date: Mon, 14 Sep 2009 08:05:32 +0300 [thread overview]
Message-ID: <4AADCF1C.80505@redhat.com> (raw)
In-Reply-To: <1252505938-3944-1-git-send-email-agraf@suse.de>
On 09/09/2009 05:18 PM, Alexander Graf wrote:
> X86 CPUs need to have some magic happening to enable the virtualization
> extensions on them. This magic can result in unpleasant results for
> users, like blocking other VMMs from working (vmx) or using invalid TLB
> entries (svm).
>
> Currently KVM activates virtualization when the respective kernel module
> is loaded. This blocks us from autoloading KVM modules without breaking
> other VMMs.
>
> To circumvent this problem at least a bit, this patch introduces on
> demand activation of virtualization. This means, that instead
> virtualization is enabled on creation of the first virtual machine
> and disabled on destruction of the last one.
>
> So using this, KVM can be easily autoloaded, while keeping other
> hypervisors usable.
>
Looks good.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-09-14 5:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 14:18 [PATCH] Activate Virtualization On Demand Alexander Graf
2009-09-14 5:05 ` Avi Kivity [this message]
2009-09-14 13:23 ` Marcelo Tosatti
2009-09-14 15:52 ` Alexander Graf
2009-09-14 16:14 ` Marcelo Tosatti
2009-09-14 16:25 ` Alexander Graf
2009-09-14 16:46 ` Marcelo Tosatti
2009-09-14 16:54 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2009-09-15 9:37 Alexander Graf
2009-03-17 8:47 Alexander Graf
2009-03-17 12:04 ` Avi Kivity
2009-03-17 15:48 ` Alexander Graf
2009-03-18 6:43 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AADCF1C.80505@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).