All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen: PV on HVM: support PV spinlocks
Date: Fri, 13 Aug 2010 14:17:53 -0700	[thread overview]
Message-ID: <4C65B681.8040408@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1008132006020.2545@kaball-desktop>

 On 08/13/2010 12:06 PM, Stefano Stabellini wrote:
> xen: PV on HVM: support PV spinlocks
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index 6f53453..5643c43 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -1290,6 +1290,8 @@ static int __cpuinit xen_hvm_cpu_notify(struct notifier_block *self,
>  	switch (action) {
>  	case CPU_UP_PREPARE:
>  		per_cpu(xen_vcpu, cpu) = &HYPERVISOR_shared_info->vcpu_info[cpu];
> +		if (xen_have_vector_callback)
> +			xen_init_lock_cpu(cpu);

Why does this depend on vector_callback?  pv spinlocks never have events
actually delivered.

Nice and simple otherwise.

    J

>  		break;
>  	default:
>  		break;
> @@ -1301,6 +1303,20 @@ static struct notifier_block __cpuinitdata xen_hvm_cpu_notifier = {
>  	.notifier_call	= xen_hvm_cpu_notify,
>  };
>  
> +static void xen_hvm_spinlock_init(void)
> +{
> +	if (!xen_have_vector_callback)
> +		return
> +	xen_init_lock_cpu(0);
> +	xen_init_spinlocks();
> +}
> +
> +static void __init xen_hvm_smp_prepare_cpus(unsigned int max_cpus)
> +{
> +	xen_hvm_spinlock_init();
> +	native_smp_prepare_cpus(max_cpus);
> +}
> +
>  static void __init xen_hvm_guest_init(void)
>  {
>  	int r;
> @@ -1320,6 +1336,7 @@ static void __init xen_hvm_guest_init(void)
>  	x86_init.irqs.intr_init = xen_init_IRQ;
>  	xen_hvm_init_time_ops();
>  	xen_hvm_init_mmu_ops();
> +	smp_ops.smp_prepare_cpus = xen_hvm_smp_prepare_cpus;
>  }
>  
>  static bool __init xen_hvm_platform(void)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2010-08-13 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 19:06 xen: PV on HVM: support PV spinlocks Stefano Stabellini
2010-08-13 21:17 ` Jeremy Fitzhardinge [this message]
2010-08-16 11:56   ` Stefano Stabellini
2010-08-16 19:43     ` Jeremy Fitzhardinge
  -- strict thread matches above, loose matches on Subject: below --
2010-10-02 11:26 Josip Rodin

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=4C65B681.8040408@goop.org \
    --to=jeremy@goop.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.