All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, avi@redhat.com, kraxel@redhat.com,
	anthony@codemonkey.ws, Sander.Vanleeuwen@sun.com,
	zach@vmware.com, brogers@novell.com
Subject: Re: [PATCH] Activate Virtualization On Demand v3
Date: Wed, 5 Nov 2008 18:58:57 -0200	[thread overview]
Message-ID: <20081105205856.GL5247@blackpad> (raw)
In-Reply-To: <1225881664-16643-1-git-send-email-agraf@suse.de>

On Wed, Nov 05, 2008 at 11:41:04AM +0100, 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 removal of the last one.
> 
> So using this, KVM can be easily autoloaded, while keeping other
> hypervisors usable.
> 
> v2 adds returns to non-x86 hardware_enables and adds IA64 change
> v3 changes:
>   - use spin_lock instead of atomics
>   - put locking to new functions hardware_{en,dis}able_all that get called
>     on VM creation/destruction
>   - remove usage counter checks where not necessary
>   - return -EINVAL for IA64 slot < 0 case
> 
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
<snip>
>  
> -static void hardware_enable(void *junk)
> +static void hardware_enable(void *_r)
>  {
>  	int cpu = raw_smp_processor_id();
> +	int r;
> +
> +	/* If enabling a previous CPU failed already, let's not continue */
> +	if (_r && *((int*)_r))
> +		return;
>  
>  	if (cpu_isset(cpu, cpus_hardware_enabled))
>  		return;
> +	r = kvm_arch_hardware_enable(NULL);
> +	if (_r)
> +		*((int*)_r) = r;
> +	if (r) {
> +		printk(KERN_INFO "kvm: enabling virtualization on "
> +				 "CPU%d failed\n", cpu);
> +		return;
> +	}
> +
>  	cpu_set(cpu, cpus_hardware_enabled);
> -	kvm_arch_hardware_enable(NULL);
> +}

Doesn't on_each_cpu() run the function in parallel on all CPUs? If so,
there is a race between checking *_r and setting *_r.

> +
> +static int hardware_enable_all(void)
> +{
> +	int r = 0;
> +
> +	spin_lock(&kvm_usage_lock);
> +	kvm_usage_count++;
> +	if (kvm_usage_count == 1)
> +		on_each_cpu(hardware_enable, &r, 1);
> +	spin_unlock(&kvm_usage_lock);
> +
> +	return r;
>  }
>  
<snip>

-- 
Eduardo

  parent reply	other threads:[~2008-11-05 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 10:41 [PATCH] Activate Virtualization On Demand v3 Alexander Graf
2008-11-05 11:49 ` Avi Kivity
2008-11-05 11:55   ` Alexander Graf
2008-11-05 12:02     ` Avi Kivity
2008-11-05 20:58 ` Eduardo Habkost [this message]
2008-11-06 12:57   ` Alexander Graf
2008-11-06 13:51     ` Eduardo Habkost

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=20081105205856.GL5247@blackpad \
    --to=ehabkost@redhat.com \
    --cc=Sander.Vanleeuwen@sun.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=brogers@novell.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=zach@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.